CVE-2026-32977: OpenClaw < 2026.3.11 - Sandbox Boundary Bypass via Unanchored writeFile Commit Path
Published Mar 31, 2026
·Updated
OpenClaw before 2026.3.11 contains a sandbox boundary bypass vulnerability in the fs-bridge writeFile commit step that uses an unanchored container path during the final move operation. An attacker can exploit a time-of-check-time-of-use race condition by modifying parent paths inside the sandbox to redirect committed files outside the validated writable path within the container mount namespace.
Affected Software
2 affected components
OpenClaw OpenClaw<2026.3.11
OpenClaw Openclaw Node.js<2026.3.11
Event History
Mar 31, 2026
CVE Published
via MITRE·11:17 AM
Data Sourced
via MITRE·11:17 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:16 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-32977?
CVE-2026-32977 is classified as a high severity vulnerability.
2
How do I fix CVE-2026-32977?
To fix CVE-2026-32977, update to OpenClaw version 2026.3.11 or later.
3
What type of attack does CVE-2026-32977 enable?
CVE-2026-32977 enables an attacker to perform a sandbox boundary bypass.
4
Which software versions are affected by CVE-2026-32977?
CVE-2026-32977 affects OpenClaw versions prior to 2026.3.11.
5
What component of OpenClaw is vulnerable in CVE-2026-32977?
CVE-2026-32977 affects the fs-bridge writeFile commit step.