Skip to main content
VulnerabilityPublished Updated

CVE-2026-32065: OpenClaw · system.run approval identity mismatch could execute a different binary than displayed

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 4.8 Medium : upgrade to 2026.2.25 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

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

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.2.25.

Affected software

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

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

AI-suggested

A patch is available and should be applied by upgrading OpenClaw CLI to version 2026.2.25 or later. This update corrects the approval identity calculation to prevent the mismatch between displayed and executed commands. No additional mitigation is required beyond applying the official fix.

Description

OpenClaw CLI versions up to 2026.2.24 have a vulnerability in the system.run approval process where the displayed command for approval can differ from the actual executed command due to trimming of whitespace in the approval identity but not in execution. This allows an attacker who can influence command arguments and reuse an approval context to bypass approval integrity and execute unexpected commands. The issue is fixed in version 2026.2.25.

References

Community reviews

Loading reviews…