Raw vector
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-32016 is a high-severity Untrusted Search Path (CWE-426) vulnerability in Openclaw Openclaw. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and CM-7 (Least Functionality) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-32016 is a path validation bypass vulnerability (CWE-426) affecting OpenClaw versions prior to 2026.2.22 on macOS. It occurs in the exec-approval allowlist mode, where basename-only allowlist entries can be exploited to execute unauthorized binaries. Specifically, attackers can run local binaries with the same name as approved ones, such as ./echo, without triggering approval prompts when security=allowlist and ask=on-miss are configured, thus circumventing intended path-based policy restrictions. The vulnerability carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
Local attackers with low privileges can exploit this issue with low complexity and no user interaction required. By placing a malicious binary with a basename matching an allowlisted entry in a different path, they bypass restrictions and execute arbitrary code, potentially leading to high confidentiality, integrity, and availability impacts on the system.
Mitigation is available in OpenClaw version 2026.2.22 and later, as detailed in the upstream patch at the referenced GitHub commit (dd41fadcaf58fd9deb963d6e163c56161e7b35dd). Security practitioners should review the GitHub Security Advisory (GHSA-7f4q-9rqh-x36p) and VulnCheck advisory for full details on the fix, which addresses the basename matching logic, and upgrade affected systems immediately.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-13281
Vulnerability Data
OpenClaw versions prior to 2026.2.22 on macOS contain a path validation bypass vulnerability in the exec-approval allowlist mode that allows local attackers to execute unauthorized binaries by exploiting basename-only allowlist entries. Attackers can execute same-name local binaries ./echo without approval…
more
when security=allowlist and ask=on-miss are configured, bypassing intended path-based policy restrictions.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Secure baseline settings can enforce absolute, organization-controlled paths for critical resources.
Least-functionality configuration can prohibit unapproved directories or executables from being reachable via search paths.
Engineering principles such as trusted paths, complete mediation, and least privilege directly require hard-coded or validated search paths instead of external ones.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Preventing execution of unauthorized code directly blocks the malicious binaries that an untrusted search path would load.
Secure development practices include avoiding or sanitizing externally influenced search paths in application code.
Hardened configuration baselines can enforce safe search paths and restrict environment variables that enable the weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can discover search-path issues but does not itself prevent them in production code.
Restricting software installation reduces the chance that untrusted binaries or libraries are placed in search paths.
Secure architecture principles include hard-coded or validated search paths and avoiding reliance on untrusted directories.
Secure coding standards require absolute paths or integrity-checked search paths, directly mitigating CWE-426.
Change-management processes can enforce review of path-handling changes, indirectly lowering risk.