CVE-2026-32921: OpenClaw < 2026.3.8 - Script Content Modification via Mutable Operand Binding in system.run
OpenClaw before 2026.3.8 contains an approval bypass vulnerability in system.run where mutable script operands are not bound across approval and execution phases. Attackers can obtain approval for script execution, modify the approved script file before execution, and execute different content while maintaining the same approved command shape.
Security readout for executives and security teams
Plain-English summary
OpenClaw versions before 2026.3.8 have a flaw in how it approves and runs scripts. An authenticated attacker can get a script approved, swap its contents on disk before it runs, and then execute different code under the original approval. This undermines the trust boundary between review and execution.
Executive priority
Plan a scheduled upgrade within the next patch cycle. Business risk is moderate, not urgent: exploitation requires an authenticated user with script submission rights, and no active abuse is cited. Prioritize sooner if OpenClaw runs in production automation with untrusted internal users or sensitive downstream actions.
Technical view
A time-of-check to time-of-use (CWE-367) race exists in system.run. Script operands are not bound between the approval phase and the execution phase, so the approved file path can be modified after approval but before execution. The engine executes the modified content while treating it as the previously approved command, bypassing review controls.
Likely exposure
Exposure is limited to environments running OpenClaw before 2026.3.8 that expose system.run to lower-privileged users through an approval workflow. CVSS 6.3 (AV:N/AC:L/PR:L/UI:N) indicates a network-reachable, low-complexity flaw requiring low privileges. Not listed in CISA KEV. No public exploitation is cited in the source bundle.
Exploitation context
Not listed in KEV and no active exploitation is cited in the provided sources. The vector requires an attacker with low privileges who can submit scripts for approval and then modify the on-disk content between approval and execution. Impact is partial across confidentiality, integrity, and availability per CVSS 3.1.
Researcher notes
CWE-367 TOCTOU where the operand (script path/content) is not bound between check and use in system.run. Investigate whether approval hashes, immutable snapshots, or file descriptor pinning are introduced by the patch commits (c76d292, cf3a479). Confirm whether approval logs record content hashes so post-hoc detection of pre-patch abuse is feasible. Evidence is limited to vendor advisory and VulnCheck writeup.
Mitigation direction
Upgrade OpenClaw to version 2026.3.8 or later on all instances.
Apply the vendor patch commits referenced in GHSA-8g75-q649-6pv6.
Restrict who can submit or approve scripts to trusted operators only.
Monitor script directories for modifications between approval and execution.
Review vendor advisory for any interim configuration guidance if upgrade is delayed.
Validation and detection
Inventory OpenClaw deployments and record installed versions.
Confirm patched hosts report 2026.3.8 or later after upgrade.
Verify the two patch commits are present in the running build's history.
Audit system.run approval and execution logs for mismatched script contents.
Retest an approval-to-execution workflow to confirm operand binding is enforced.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-367 · source CWE mapping
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.