CVE-2026-53975
CriticalCVSS 9.8Exploitation Probability (EPSS)
Elevated risk64th percentile - higher than 64% of all known CVEs
Summary
Unauthenticated remote code execution vulnerability in OpenChamber 1.11.7, allowing remote attackers to execute arbitrary shell commands by sending crafted POST requests to /api/fs/exec, which passes commands verbatim to Node.js spawn() without validation.
Risk Assessment
An attacker can execute arbitrary OS commands as the application user, potentially leading to full system compromise and data leakage.
Recommendation
Update OpenChamber to a patched version or configure UI_PASSWORD to enable authentication, and restrict access to the /api/fs/exec endpoint.
Other vulnerabilities in OpenChamber
See all- CVE-2026-53976Critical
Path traversal vulnerability in OpenChamber 1.11.7 in file-serving endpoints /api/fs/read, /api/fs/stat, and /api/fs/raw, allowing unauthenticated remote attackers to read arbitrary files by supplying allowOutsideWorkspace=true and an absolute path, bypassing workspace boundary check.
- CVE-2026-53977High
OpenChamber 1.11.7 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to terminate the server process by sending a POST request to the /api/system/shutdown endpoint, which is registered before the authentication middleware in the Express route handler chain. Attackers can exploit the route registration order in bootstrap-runtime.js to reach the shutdown handler before auth middleware executes, causing denial of service to all active AI coding sessions and locking out legitimate remote users regardless of whether UI_PASSWORD is configured.
Original NVD description (English source)
OpenChamber 1.11.7 contains an unauthenticated remote code execution vulnerability that allows remote attackers to execute arbitrary shell commands by sending crafted POST requests to the /api/fs/exec endpoint, which passes commands verbatim to Node.js spawn() without any allowlist, blocklist, or argument validation. The authentication middleware becomes a no-op when UI_PASSWORD is not configured, matching the default Docker deployment, enabling attackers to execute arbitrary OS commands as the application user and retrieve full command output including stdout, stderr, and exit code from the server response.