PatchSiren cyber security CVE debrief
CVE-2026-53975 Bohdan Triapitsyn CVE debrief
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 vulnerability enables 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 when UI_PASSWORD is not configured, matching the default Docker deployment. Evidence is limited to public sources and may not reflect the full scope or impact of the vulnerability. Defenders should verify affected deployments, review official advisories, and monitor for suspicious activity. The CVE record was published on 2026-08-06T15:16:55.827Z and has not been modified since then. This vulnerability has a CVSS score of 9.3 and a severity of CRITICAL.
- Vendor
- Bohdan Triapitsyn
- Product
- OpenChamber
- CVSS
- CRITICAL 9.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-06
- Original CVE updated
- 2026-09-16
- Advisory published
- 2026-08-06
- Advisory updated
- 2026-09-16
Who should care
Users of OpenChamber 1.11.7, especially those with default Docker deployments or exposed /api/fs/exec endpoints, should prioritize remediation due to the critical severity and unauthenticated nature of the vulnerability. Operators, security teams, and vulnerability management teams should review affected scope, plan vendor-supported updates or mitigations, and implement compensating controls for exposed systems.
Technical summary
The vulnerability 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 validation or sanitization. This occurs when UI_PASSWORD is not configured, such as in default Docker deployments. The vulnerability enables attackers to execute arbitrary OS commands as the application user and retrieve full command output.
Defensive priority
High
Recommended defensive actions
- Inventory OpenChamber 1.11.7 deployments and verify UI_PASSWORD configuration
- Restrict access to the /api/fs/exec endpoint
- Implement allowlisting or blocklisting for Node.js spawn() commands
- Monitor for suspicious POST requests to /api/fs/exec
- Apply vendor remediation when available
Evidence notes
The vulnerability allows remote 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 when UI_PASSWORD is not configured, matching the default Docker deployment. Evidence is limited to public sources and may not reflect the full scope or impact of the vulnerability. Defenders should verify affected deployments, review official advisories, and monitor for suspicious activity.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-53975 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-53975
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-53975 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-53975
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/openchamber/openchamber
-
Source reference
Unverified legacy reference
URL: https://github.com/openchamber/openchamber/commit/f1b9506132faf6c564a2694c7f33b94421a49b4a
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/openchamber-unauthenticated-rce-via-api-fs-exec
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.