CVE-2026-32973: OpenClaw · Exec approval allowlist patterns overmatched on POSIX paths
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 6.9 Medium : upgrade to 2026.3.11 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.3.11
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 16 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.3.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
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. The issue is fixed in openclaw version 2026.3.11 and later releases such as 2026.3.12. Users should upgrade to these versions to ensure correct exec allowlist matching behavior that respects POSIX path semantics.
Description
OpenClaw CLI versions before 2026.3.11 have a flaw in their exec allowlist pattern matching on POSIX paths. The matching function overmatches due to lowercasing normalization and glob pattern handling, allowing the '?' wildcard to match path separators. This can cause unintended commands or executable paths to be approved by the operator. The issue is fixed in version 2026.3.11 and later.