CVE-2026-105641
Deferred Deferred - Pending Action

Hard-Coded Secrets in Plane Project Management Tool

Vulnerability report for CVE-2026-105641, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-05

Last updated on: 2026-10-05

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-05
Last Modified
2026-10-05
Generated
2026-10-05
AI Q&A
2026-10-05
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
makeplane plane < 1.4.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-798 The product contains hard-coded credentials, such as a password or cryptographic key.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves hardcoded SECRET_KEY and LIVE_SERVER_SECRET_KEY values in Plane's community deployment manifests. These keys are publicly known and used as defaults if not overridden, allowing attackers to forge Django-signed values like session tokens or bypass live-service authentication. The issue affects versions before 1.4.0.

Detection Guidance

Check Plane deployment manifests for hardcoded SECRET_KEY and LIVE_SERVER_SECRET_KEY values in community deployments. Inspect plane.env and docker-compose.yml files for default or placeholder keys. Run start.sh and check for security warnings about insecure keys.

Impact Analysis

Attackers can exploit this to forge session tokens, reset passwords, or bypass authentication for live collaboration features. This could grant full access to workspace data without prior authentication, compromising confidentiality, integrity, and availability of the system.

Compliance Impact

This vulnerability likely violates compliance requirements for data protection (e.g., GDPR, HIPAA) due to unauthorized access risks, lack of proper authentication, and potential exposure of sensitive user data. Organizations using affected versions must remediate to maintain compliance.

Mitigation Strategies

Upgrade to Plane version 1.4.0 or later. Regenerate SECRET_KEY and LIVE_SERVER_SECRET_KEY using start.sh for AIO deployments or update docker-compose.yml and variables.env for CLI deployments. Remove any hardcoded keys and ensure random key generation on first run.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-105641. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart