Security readout for executives and security teams
Plain-English summary
OpenClaw versions before 2026.3.11 have a flaw in how the sandbox finalizes file writes. A local user with low privileges can time a race and swap parent folders so files land outside the protected area. This can let an attacker tamper with or destroy data the sandbox was meant to isolate, weakening a security boundary the product exists to enforce.
Executive priority
Patch on the next scheduled maintenance window. Impact is bounded by the need for local, low-privilege access and high attack complexity, but the flaw undermines a sandbox trust boundary, so multi-tenant or shared-workload environments should treat it as a near-term fix rather than deferring indefinitely.
Technical view
The fs-bridge writeFile commit step uses an unanchored container path during the final move. A local attacker with sandbox access exploits a CWE-367 time-of-check-time-of-use race by mutating parent path components between validation and the commit rename, redirecting the committed file outside the validated writable path within the container mount namespace. CVSS 3.1 6.3 (AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H) reflects local access, high complexity, and impact on integrity and availability.
Likely exposure
Environments running OpenClaw before 2026.3.11 that rely on the fs-bridge sandbox to isolate tenant, plugin, or workload file writes. Exposure is limited to actors who already have local, low-privilege execution inside the sandbox, so the impact concentrates on multi-tenant hosts and CI or automation nodes that treat the sandbox as a trust boundary.
Exploitation context
No public exploitation is cited and the CVE is not listed in CISA KEV. The advisory describes a race-condition path that requires local access and precise timing, reflected in the CVSS high attack complexity. No proof-of-concept, exploit tooling, or in-the-wild activity is referenced in the provided sources.
Researcher notes
CWE-367 TOCTOU between path validation and the final move in fs-bridge writeFile. Root cause is an unanchored container path allowing parent-directory manipulation during the commit rename. Look for symlink or directory swap races on parents of the target write path. CVSS Scope:U indicates impact stays within the sandboxed component, but integrity and availability outside the intended writable path are the practical concern. No KEV, no cited PoC.
Mitigation direction
- Upgrade OpenClaw to 2026.3.11 or later on all affected hosts.
- Consult the GitHub Security Advisory GHSA-xvx8-77m6-gwg6 for vendor-supplied guidance.
- Restrict local sandbox access to trusted, authenticated workloads only.
- Monitor filesystem activity for writes committed outside expected sandbox paths.
- Where upgrade is delayed, harden mount namespaces and reduce untrusted code execution in the sandbox.
Validation and detection
- Inventory OpenClaw deployments and confirm versions against the 2026.3.11 fix line.
- Verify patched builds via package manager or container image digest after upgrade.
- Review fs-bridge configuration for writable paths that could be redirected via parent components.
- Audit logs for anomalous rename or move operations from sandboxed processes.
- Retest sandbox boundary with vendor or internal integrity checks post-upgrade.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-367: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-32977 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H15.2VulnCheckCVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
5.8MediumVector: CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-xvx8-77m6-gwg6)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: OpenClaw < 2026.3.11 - Sandbox Boundary Bypass via Unanchored writeFile Commit PathCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.