Skip to main content
Vulnerability Database/CVE-2026-105637

CVE-2026-105637: Plane Project Management Auth Bypass Flaw

CVE-2026-105637 is an authentication bypass vulnerability in Plane that allows workspace guests to hijack assets from other projects by manipulating asset UUIDs. This post covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-105637 Overview

Plane is an open-source project management tool used by teams for issue tracking, documentation, and collaboration. CVE-2026-105637 is an Insecure Direct Object Reference (IDOR) vulnerability in the ProjectBulkAssetEndpoint.post handler located in apps/api/plane/app/views/asset/v2.py. The flaw allows a workspace Guest to hijack assets belonging to other projects within the same workspace. Attackers reassign ownership of files to entities they control and then retrieve presigned download URLs for those files. The vulnerability is tracked under [CWE-639] and is fixed in Plane version 1.4.0.

Critical Impact

Low-privileged workspace Guests can hijack and download arbitrary files uploaded by other projects in the same workspace, exposing confidential issue attachments, comments, pages, and draft content.

Affected Products

  • Plane (makeplane/plane) versions prior to 1.4.0
  • Self-hosted and cloud Plane deployments running vulnerable API versions
  • Any workspace permitting Guest-level accounts across multiple projects

Discovery Timeline

  • 2026-10-05 - CVE-2026-105637 published to the National Vulnerability Database (NVD)
  • 2026-10-05 - Last updated in NVD database

Technical Details for CVE-2026-105637

Vulnerability Analysis

The vulnerability resides in the bulk asset association endpoint ProjectBulkAssetEndpoint.post. The handler queries assets using id__in=asset_ids combined with workspace__slug=slug but omits the project_id constraint carried in the URL. As a result, any asset UUID known to the attacker and belonging to the same workspace resolves successfully.

Once the query returns, the endpoint reassigns asset attributes such as issue_id, comment_id, page_id, draft_issue_id, or project_id to entities controlled by the caller. The API then treats the attacker's project as the new owner of the asset and generates a presigned download URL. Confidential attachments from unrelated projects become retrievable by a user who should have no access to them.

Exploitation requires only a workspace Guest account and knowledge or enumeration of asset UUIDs. No user interaction is required, and the scope changes because the attacker crosses the project authorization boundary within a shared workspace.

Root Cause

The root cause is missing authorization scoping in the ORM query. The endpoint trusts that workspace__slug alone constrains asset access, but Plane's permission model separates projects within a workspace. Without filtering by project_id and verifying the uploader, the query returns assets that the authenticated Guest has no entitlement to modify.

Attack Vector

An authenticated workspace Guest submits a POST request to the bulk asset endpoint for a project they legitimately access. The request body references asset UUIDs that belong to other projects in the same workspace. The server reassigns ownership of those assets and returns presigned URLs the attacker uses to download the hijacked files directly from object storage.

python
 from django.http import HttpResponseRedirect
 from django.utils import timezone
 from django.db import IntegrityError
+from django.db.models import Q
 
 # Third party imports
 from rest_framework import status

Source: GitHub Commit 15e8357. The patch introduces additional query predicates to scope bulk-asset association by uploader rather than relying on project_id from the URL alone.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-105637

Indicators of Compromise

  • POST requests to the ProjectBulkAssetEndpoint referencing asset UUIDs that do not match assets previously uploaded under the targeted project
  • Sudden changes to asset project_id, issue_id, comment_id, page_id, or draft_issue_id fields in the Plane database without a corresponding upload event
  • Presigned object storage URLs issued to Guest accounts for files they did not create
  • Access log entries where Guest users retrieve attachments shortly after bulk asset association calls

Detection Strategies

  • Audit application logs for bulk asset association requests originating from Guest-level roles and correlate them with the ownership of referenced asset IDs
  • Compare current asset ownership (project_id, uploader) against historical values to detect unauthorized reassignment
  • Monitor object storage access logs for presigned URL downloads of attachments by users outside the originating project

Monitoring Recommendations

  • Enable verbose API audit logging on the /api/v1/workspaces/{slug}/projects/{project_id}/bulk-assets/ route
  • Alert on high-volume POST requests to the bulk asset endpoint from a single Guest account
  • Track database writes that modify asset foreign keys and flag changes performed by non-admin workspace roles

How to Mitigate CVE-2026-105637

Immediate Actions Required

  • Upgrade all Plane instances to version 1.4.0 or later immediately
  • Review Guest role memberships across workspaces and remove accounts that are not strictly required
  • Audit asset ownership records to identify any unauthorized reassignments made before the patch was applied
  • Rotate or invalidate outstanding presigned URLs where the storage backend supports it

Patch Information

The fix is included in Plane 1.4.0. See the GitHub Release v1.4.0, the GitHub Security Advisory GHSA-r2hw-fff3-pjwp, and the GitHub Pull Request Discussion for full remediation details. The patch scopes bulk asset association by uploader rather than relying on the URL-provided project_id.

Workarounds

  • Temporarily restrict Guest accounts from workspaces that contain sensitive attachments until the upgrade is complete
  • Place the Plane API behind a reverse proxy rule that blocks requests to the bulk asset endpoint from non-admin roles
  • If an upgrade is not immediately possible, disable the bulk asset association route at the application gateway
bash
# Verify your Plane version before and after upgrade
docker exec plane-api python -c "import plane; print(plane.__version__)"

# Pull the patched release
docker pull makeplane/plane-api:v1.4.0
docker compose up -d

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.