Skip to main content
CVE-2026-32058VulnerabilityPublished Updated

Openclaw cli: OpenClaw Node system.run approval context-binding weakness in approval-enabled host=node flows

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 2.6 Low : upgrade to 2026.2.26 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
2.6Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.2.26
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/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.26.

Affected software

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

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 in OpenClaw CLI version 2026.2.26 that enforces strict, versioned execution-context binding for system.run approvals in host=node workflows. Users should upgrade to version 2026.2.26 or later to remediate this issue. No additional mitigation actions are required beyond applying the official fix.

Description

A medium-severity vulnerability in OpenClaw CLI affects approval-enabled workflows using host=node for system.run commands. The issue arises because system.run approvals did not enforce strict, versioned execution-context binding, allowing a previously approved request to be reused with altered environment input in certain configurations. The vulnerability requires specific conditions including exec approvals enabled, system.run usage via host=node, and access to an approval ID in the same context. A fix is planned in version 2026.2.26 that enforces versioned binding and removes legacy fallback matching.

References

Community reviews

Loading reviews…