CVE-2026-102986 makeplane CVE debrief

Who should care

Defenders responsible for Plane deployments should assess exposure and take remediation actions, including verifying project configurations and upgrading to version 1.4.0 or later. Operators, platform administrators, vulnerability management teams, and security teams should review the vulnerability details and take necessary actions to protect their assets. The vulnerability poses risks of data loss and storage abuse, and defenders should prioritize remedi

Why it matters

CVE-2026-102986 allows authenticated users to inject files and delete assets in any published project in Plane versions 1.3.1 and earlier, posing risks of data loss and storage abuse. Defenders should verify exposure, review project configurations, and upgrade to version 1.4.0 or later.

• Potential for cross-workspace file injection and data loss.
• Possible storage abuse through unauthorized asset uploads.
• Risk of asset deletion leading to data loss.
• Need for verification of project configurations and user access controls.

Technical summary

The EntityAssetEndpoint in Plane versions 1.3.1 and earlier does not verify workspace or project membership for write operations, allowing authenticated users to inject files and delete assets in any published project. This issue is fixed in version 1.4.0. Defenders should prioritize verifying exposure and upgrading to version 1.4.0 or later. The vulnerability poses risks of data loss and storage abuse, and defenders should review project configurations to ensure proper authorization and access controls. The CVE record and source item provide details on the vulnerability.

Defensive priority

Defenders should prioritize verifying exposure and upgrading to version 1.4.0 or later.

Recommended defensive actions

• Verify if Plane versions 1.3.1 or earlier are in use and upgrade to version 1.4.0 or later.
• Review project configurations to ensure proper authorization and access controls.
• Monitor for suspicious asset upload and deletion activities.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Evidence notes

The CVE record and source item provide details on the vulnerability in Plane versions 1.3.1 and earlier. The issue is fixed in version 1.4.0. Defenders should verify exposure, review project configurations, and upgrade to version 1.4.0 or later. The CVE Program record and NVD vulnerability detail provide additional information on the vulnerability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.