Skip to main content
CVE-2026-31997VulnerabilityPublished Updated

openclaw-cli · OpenClaw: system.run approvals did not bind PATH-token executable identity, enabling post-approval executable rebind

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 2026.3.1 soon.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA: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 19 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.1.

Affected software

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

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.3.1 that fixes this issue by enforcing immutable systemRunPlan data and pinning executable identities. Users should upgrade to version 2026.3.1 or later to remediate this vulnerability.

Description

OpenClaw CLI versions up to 2026.2.26 have a vulnerability where system.run approvals do not bind the executable identity for commands resolved via PATH tokens. This allows a previously approved action to execute a different binary if the PATH resolution changes after approval. The issue is fixed in version 2026.3.1 by requiring immutable systemRunPlan data and pinning path-token commands to their canonical executable identity.

References

Community reviews

Loading reviews…