CVE-2026-105641

Plane: Hardcoded SECRET_KEY and LIVE_SERVER_SECRET_KEY shipped in aio/cli community deployment manifests — session forgery and live-server auth bypass

Published Oct 5, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
Plane is an open-source project management tool. Prior to 1.4.0, the deployments/aio/community/ and deployments/cli/community/ manifests provide fixed, publicly known SECRET_KEY and LIVE_SERVER_SECRET_KEY defaults that remain active when operators do not override them. The top-level setup.sh randomizes secrets only for the development Docker Compose path, leaving unchanged aio and cli community deployments with shared production secrets. Knowledge of SECRET_KEY enables attackers to forge Django-signed values and compromise accounts or sessions. Knowledge of LIVE_SERVER_SECRET_KEY bypasses live-service authentication on unchanged community deployments. This issue is fixed in 1.4.0.

Analysis

AI-generated

Technical impact

Plane shipped default values for SECRET_KEY and LIVE_SERVER_SECRET_KEY in community deployment manifests before version 1.4.0. The hardcoded keys are publicly known and allow an attacker who can read the manifests to forge Django‑signed values, thereby compromising user accounts or forging sessions. The exposed LIVE_SERVER_SECRET_KEY also provides a method to bypass authentication for the live‑service. This flaw represents an insecure default (CWE-798).

Affected Systems

The vulnerability affects makeplane’s Plane project management tool. All installations that use the aio/cli community deployment manifests with the default keys and are running any version earlier than 1.4.0 are impacted. The fix is released in 1.4.0. The impacted products are Plane under the community deployment path, with unspecified version detail but any pre‑1.4.0 release.

Risk and Exploitability

The CVSS score is 9.8, indicating critical severity. EPSS data is not available, but the lack of offline secrets and the fact that the default keys are contained in publicly visible GitHub repositories suggest a high likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog. An attacker can exploit the flaw remotely by simply cloning the repository and extracting the secrets, then using the keys to forge session data or bypass live-service authentication. No known exploitation has been reported yet, but the risk remains high for any deployment that has not overridden the default keys.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Plane to version 1.4.0 or later to remove the hardcoded secrets.
  • If you cannot immediately upgrade, replace the hardcoded SECRET_KEY and LIVE_SERVER_SECRET_KEY values in the aio/cli community deployment manifests with unique, randomly generated secrets before deploying the application.
  • If upgrading is not possible or you are reusing community manifests, ensure the new secrets are injected via environment variables or a secrets manager so that the defaults are not used at runtime.

Generated by OpenCVE AI on October 5, 2026 at 20:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Makeplane
Makeplane plane
Vendors & Products Makeplane
Makeplane plane
Type Values Removed Values Added
Description Plane is an open-source project management tool. Prior to 1.4.0, the deployments/aio/community/ and deployments/cli/community/ manifests provide fixed, publicly known SECRET_KEY and LIVE_SERVER_SECRET_KEY defaults that remain active when operators do not override them. The top-level setup.sh randomizes secrets only for the development Docker Compose path, leaving unchanged aio and cli community deployments with shared production secrets. Knowledge of SECRET_KEY enables attackers to forge Django-signed values and compromise accounts or sessions. Knowledge of LIVE_SERVER_SECRET_KEY bypasses live-service authentication on unchanged community deployments. This issue is fixed in 1.4.0.
Title Plane: Hardcoded SECRET_KEY and LIVE_SERVER_SECRET_KEY shipped in aio/cli community deployment manifests — session forgery and live-server auth bypass
Weaknesses CWE-798
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-798

    Use of Hard-coded Credentials

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 7, 2026, 9:40 PM
Reserved
Oct 5, 2026, 4:40 PM
Status
Deferred
Published
Oct 5, 2026, 7:17 PM
Modified
Oct 7, 2026, 10:17 PM