Skip to main content
CVE-2026-32921VulnerabilityPublished Updated

Openclaw cli: OpenClaw's system.run approvals did not bind mutable script operands across approval and execution

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2026.3.8 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.8.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.3.8
Fixed in
  • 2026.3.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade OpenClaw CLI to version 2026.3.8 or later, which contains the complete fix binding approved script operands to immutable on-disk snapshots, preventing script content changes after approval. No additional mitigation is required once the update is applied.

Description

OpenClaw CLI versions up to 2026.3.7 have a vulnerability in the system.run approval flow where mutable script operands were not properly bound across approval and execution. This allowed an attacker to modify the script content after approval but before execution, causing different code to run under an approved command shape. The issue was fully fixed in version 2026.3.8 by binding approved script operands to on-disk file snapshots, preventing post-approval script drift.

References

Community reviews

Loading reviews…