Is CVE-2026-105632 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-105632 being exploited in the wild.

How severe is CVE-2026-105632?

Informational severity, published 5 October 2026.

Is there a fix for CVE-2026-105632?

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-105632 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-105632?

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.

CVE-2026-105632: Plane project management authorization bypass in GraphQL

CVE-2026-105632 · Severity: info · Published 2026-10-05

Plane is an open-source project management tool that organizes work across workspaces and projects. A flaw in the GraphQL API allowed any workspace member to automatically grant themselves access to private projects they were never invited to, potentially exposing confidential project data. This breaks the isolation between projects and allows low-privilege users to read and modify sensitive information in any private project within their workspace.

Technologies: Plane. Vendors: Plane.

Quick answers

Is CVE-2026-105632 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105632 being exploited in the wild.
How severe is CVE-2026-105632?: Informational severity, published 5 October 2026.
Which products and versions are affected?: Plane prior to 1.4.0.
Is there a fix for CVE-2026-105632?: 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-105632 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-105632?: 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

The GraphQL joinProject mutation failed to validate project visibility (network setting) when checking permissions; it only verified workspace-level membership. An authenticated workspace member could invoke joinProject on any project UUID in the workspace—including network=0 (secret/private) projects—and gain full Member role without an invitation. The resolver did not check the target project's visibility or the user's project-level permissions, only workspace-level role, allowing tenant isolation bypass within a workspace.

Affected products

Plane Plane prior to 1.4.0

Timeline

2026-10-05: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.