Quick answers
- Is CVE-2026-105641 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105641 being exploited in the wild.
- How severe is CVE-2026-105641?
- Critical severity, with a CVSS score of 9.8, published 5 October 2026.
- Which products and versions are affected?
- Plane prior to 1.4.0.
- Is there a fix for CVE-2026-105641?
- Yes: fixed in 1.4.0. Until then: Ensure all deployments override SECRET_KEY and LIVE_SERVER_SECRET_KEY with unique random values in their environment configuration before deploying to production. The start.sh script in version 1.4.0 auto-generates random keys on first boot if placeholder values are detected. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105641 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-105641?
- 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
Ensure all deployments override SECRET_KEY and LIVE_SERVER_SECRET_KEY with unique random values in their environment configuration before deploying to production. The start.sh script in version 1.4.0 auto-generates random keys on first boot if placeholder values are detected.
Technical details
Prior to version 1.4.0, Plane's AIO and CLI community deployment manifests embedded fixed SECRET_KEY and LIVE_SERVER_SECRET_KEY values in configuration files. An attacker with knowledge of these public secrets can forge Django-signed session tokens to impersonate users or bypass the live-service authentication mechanism. The vulnerability requires network access to a vulnerable deployment but no authentication or user interaction.
Affected products
- Plane Plane prior to 1.4.0
Timeline
- 2026-10-05: disclosed
- 2026-06-23: patched