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-105631 Overview
Plane, an open-source project management tool, contains an Insecure Direct Object Reference (IDOR) flaw in its file asset endpoints prior to version 1.4.0. The WorkspaceFileAssetEndpoint.get and WorkspaceAssetDownloadEndpoint.get handlers resolve FileAsset records within a workspace without verifying membership in the asset's project. A workspace member can download assets from private projects when the asset UUID is known. A separate endpoint, EntityAssetEndpoint.get, grants AllowAny access and scopes lookups only to the anchor's workspace. An unauthenticated caller who knows a valid anchor and asset UUID can retrieve issue-description or comment-description assets from unpublished or private projects. The flaw is tracked as [CWE-639] and fixed in version 1.4.0.
Critical Impact
Unauthenticated or low-privileged attackers can exfiltrate private project assets, including issue and comment attachments, by guessing or discovering asset UUIDs within a workspace.
Affected Products
- Plane (makeplane/plane) versions prior to 1.4.0
- WorkspaceFileAssetEndpoint and WorkspaceAssetDownloadEndpoint handlers
- EntityAssetEndpoint public-anchor endpoint
Discovery Timeline
- 2026-10-05 - CVE-2026-105631 published to NVD
- 2026-10-07 - Last updated in NVD database
Technical Details for CVE-2026-105631
Vulnerability Analysis
The vulnerability stems from permission checks that validate workspace membership but omit project-level authorization. When a user requests a FileAsset, the endpoints resolve the record using the asset UUID and workspace scope only. Any authenticated workspace member can request assets belonging to projects they do not have access to. The EntityAssetEndpoint compounds the exposure by allowing anonymous callers to resolve assets through a public anchor without checking whether the parent entity is published. Attackers who know or enumerate asset UUIDs can retrieve issue descriptions, comment attachments, and other file content from private projects.
Root Cause
The root cause is missing authorization at the project boundary. Permission classes verified that the request originated from a valid workspace member but did not join the lookup against ProjectMember. The code imported WorkspaceMember but lacked a corresponding ProjectMember check for assets scoped to a project. For the public-anchor path, the endpoint used AllowAny and resolved assets by workspace alone, ignoring the published state of the parent entity.
Attack Vector
Exploitation requires network access to a Plane instance and knowledge of an asset UUID. For the authenticated path, the attacker must hold any role in the target workspace. For the EntityAssetEndpoint path, the attacker needs a valid anchor and asset UUID but no credentials. UUIDs may be obtained through log exposure, referrer leakage, or systematic enumeration.
# Patch: new permission class scoping access to active workspace members
# Source: https://github.com/makeplane/plane/commit/4577dc3f7a6b5a198602b602a45c6b0abdc7204b
class WorkspaceMemberPermission(BasePermission):
"""Allows access only to active workspace members.
Resolves the workspace via 'slug' or 'workspace_id' in URL kwargs so this
class can be used on endpoints that identify the workspace by either
identifier (e.g. FileAssetEndpoint which mixes both URL patterns).
"""
def has_permission(self, request, view):
if request.user.is_anonymous:
return False
workspace_id = view.kwargs.get("workspace_id")
if workspace_id:
return WorkspaceMember.objects.filter(
workspace_id=workspace_id, member=request.user, is_active=True
).exists()
slug = view.kwargs.get("slug")
if slug:
return WorkspaceMember.objects.filter(
workspace__slug=slug, member=request.user, is_active=True
).exists()
return False
The follow-up patch in apps/api/plane/app/views/asset/v2.py adds ProjectMember to the imports, enabling project-scope checks on asset get, patch, and delete operations. See GitHub Commit e63f0c3 for the full change.
Detection Methods for CVE-2026-105631
Indicators of Compromise
- Unexpected GET requests to /api/workspaces/<slug>/file-assets/<uuid>/ or asset download routes from accounts without a legitimate business need in the parent project.
- Anonymous requests to EntityAssetEndpoint referencing anchors from unpublished entities.
- Spikes in 200-response asset downloads correlated with sequential or scripted UUID access patterns.
Detection Strategies
- Review web and application access logs for requests to FileAsset endpoints that originate from users not listed in the asset's parent ProjectMember table.
- Correlate asset download events with project membership records to identify cross-project access attempts.
- Alert on anonymous or unauthenticated hits to entity-asset routes outside of normal published-page traffic.
Monitoring Recommendations
- Enable verbose request logging on Plane API endpoints handling FileAsset objects.
- Forward Plane application logs into a centralized analytics platform for retrospective review and correlation with user-role data.
- Track per-user asset download volumes and flag deviations from historical baselines.
How to Mitigate CVE-2026-105631
Immediate Actions Required
- Upgrade Plane to version 1.4.0 or later, which introduces the WorkspaceMemberPermission class and project-scope checks.
- Audit historical access logs for suspicious asset downloads from workspace members outside the parent project.
- Rotate or review sensitive content hosted in private project issues and comments if unauthorized access is suspected.
Patch Information
The fix is distributed in Plane release v1.4.0. The underlying code changes are documented in GitHub Pull Request #9288 and GitHub Pull Request #9372, with details in the GitHub Security Advisory GHSA-85h2-mhcc-xfmw.
Workarounds
- Restrict network exposure of the Plane API to trusted users through a reverse proxy or VPN until the upgrade is applied.
- Disable or firewall the public-anchor EntityAssetEndpoint routes if published-page functionality is not required.
- Minimize the number of workspace members with access to workspaces that contain sensitive private projects.
# Upgrade example for self-hosted Docker deployments
docker compose pull
docker compose down
docker compose up -d
# Verify the running version matches v1.4.0 or later
docker exec -it plane-api sh -c 'cat /app/VERSION'
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

