Quick answers
- Is CVE-2026-104966 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104966 being exploited in the wild.
- How severe is CVE-2026-104966?
- Informational severity, published 5 October 2026.
- Which products and versions are affected?
- Plane before 1.4.0.
- Is there a fix for CVE-2026-104966?
- Yes: fixed in 1.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104966 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104966?
- Check whether you run Plane at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.4.0
Technical details
Two endpoint families fail to verify that nested resource identifiers belong to the workspace and project in the URL: PATCH /api/workspaces/{slug}/projects/{project_id}/estimates/{estimate_id}/ and POST /api/workspaces/{slug}/projects/{project_id}/issues/{issue_id}/comments/. The ProjectEntityPermission middleware correctly validates workspace and project membership, but the estimate_id and issue_id are fetched by primary key alone without confirming they belong to that workspace and project scope. An authenticated attacker can exploit this insecure direct object reference (IDOR) to read/modify estimates or inject comments across workspace boundaries. The fix adds workspace and project scoped ownership checks before creating or modifying these nested resources.
Affected products
- Plane Plane before 1.4.0
Timeline
- 2026-10-05: disclosed