OpenChamber 1.11.7 Vulnerability: Critical Remote Code Execution Risk
An early warning has been issued regarding a critical vulnerability in OpenChamber 1.11.7, which reportedly allows unauthenticated remote code execution via crafted POST requests.
What happened
OpenChamber 1.11.7 is under investigation for containing an unauthenticated remote code execution vulnerability. This vulnerability, tracked as CVE-2026-53975, allows attackers to execute arbitrary shell commands by sending crafted POST requests to the /api/fs/exec endpoint. The issue arises because commands are passed verbatim to Node.js spawn() without any validation, and the authentication middleware becomes ineffective when UI_PASSWORD is not configured, which is the default in Docker deployments.
Additionally, OpenChamber 1.11.7 appears to have a path traversal vulnerability, tracked as CVE-2026-53976, which allows unauthenticated remote attackers to read arbitrary files by supplying specific query parameters. This can lead to the exposure of sensitive files such as JWT signing secrets, SSH private keys, API credentials, and environment variables.
Professional software engineers using OpenChamber 1.11.7 are advised to assess their exposure to these vulnerabilities. It is recommended to upgrade to a patched version of OpenChamber as soon as it becomes available. For more detailed information, primary sources should be consulted.
How 0Day mitigates this
openchamber is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.