CVE-2026-53975 Bohdan Triapitsyn CVE debrief

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.

Official resources