Security readout for executives and security teams
Plain-English summary
OpenClaw versions before 2026.3.11 can let a low-privileged local attacker bypass intended sandbox file boundaries. The issue can allow attacker-controlled writes outside the validated path, creating material integrity and availability risk where OpenClaw protects filesystem operations.
Executive priority
Treat this as a high-priority patching item for systems where OpenClaw enforces filesystem isolation. Urgency is lower than confirmed exploited bugs, but impact is meaningful if attackers already have local low-privileged access.
Technical view
The flaw is a CWE-367 race condition in fs-bridge staged writes. Temporary file creation and population are not pinned to a verified parent directory, so parent-path alias changes can redirect writes before the final guarded replace step.
Likely exposure
Systems running OpenClaw before 2026.3.11 are the likely exposure, especially deployments relying on sandboxed filesystem writes. The bundle provides no CPEs, so version inventory is the primary scoping method.
Exploitation context
The CVSS vector indicates local access, low privileges, no user interaction, high complexity, and changed scope. KEV is false, and the provided sources do not establish active exploitation.
Researcher notes
Focus review on path validation, temporary file parent pinning, and race resistance around staged writes. The source bundle does not include exploit code, CPEs, or evidence of exploitation in the wild.
Mitigation direction
- Upgrade OpenClaw to 2026.3.11 or later.
- Review the GitHub advisory for vendor-specific remediation guidance.
- Prioritize hosts where OpenClaw mediates writes across trust boundaries.
- Restrict local low-privileged access where feasible until patched.
- Monitor vendor and CVE records for additional guidance.
Validation and detection
- Inventory OpenClaw versions across endpoints, build images, and developer environments.
- Flag any OpenClaw installation earlier than 2026.3.11.
- Identify workflows using fs-bridge staged writes or sandboxed file operations.
- Confirm upgraded systems report OpenClaw 2026.3.11 or later.
- Review logs for unexpected writes outside intended sandbox paths.
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 lookupCVE-2026-32988 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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:C/C:N/I:H/A:H1.15.8VulnCheckCVSS: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
7.5HighVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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-mj4p-rc52-m843)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: OpenClaw < 2026.3.11 - Sandbox Boundary Bypass via Unvalidated Temporary File CreationCVE 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.