Skip to main content
VulnerabilityPublished Updated

CVE-2026-32016: OpenClaw · macOS optional allowlist basename matching could bypass path-based policy

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.8 High : upgrade to 2026.7.1 soon.

Data as of 17 Nov 2026, 20:25 UTC

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

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

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • <2026.7.1
Fixed in
  • 2026.7.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 and planned for OpenClaw CLI version 2026.2.22 that enforces path-only allowlist matching and removes basename fallback. Users should upgrade to version 2026.2.22 or later once released. The default security posture 'security=deny' is not affected, so users not using 'security=allowlist' mode are not impacted. No additional mitigation is required beyond applying the official fix when available.

Description

OpenClaw CLI on macOS has a vulnerability in its optional exec-approval allowlist mode where basename-only entries are treated as trusted commands. This allows a local binary with the same name as an allowed command to execute without approval under certain security settings. The default security posture is not affected. A patch is planned in version 2026.2.22 to enforce path-only allowlist matching and remove basename fallback.

References

Community reviews

Loading reviews…