CVE-2026-29610
Openclaw ≤ 2026.2.14
Raw vector
CVSS:4.0/AV:N/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-29610 is a high-severity Uncontrolled Search Path Element (CWE-427) vulnerability in Openclaw Openclaw. Its CVSS base score is 7.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 38th 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 AC-3 (Access Enforcement) — 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-29610 is a command hijacking vulnerability (CWE-427) affecting OpenClaw versions prior to 2026.2.14. The flaw enables attackers to execute unintended binaries by manipulating PATH environment variables during node-host execution or project-local bootstrapping processes.
Attackers with authenticated access to node-host execution surfaces, or those running OpenClaw in attacker-controlled directories, can exploit this by placing malicious executables in the PATH to override allowlisted safe-bin commands, resulting in arbitrary command execution. The vulnerability carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating high impact with network accessibility, low attack complexity, and low privileges required.
Advisories recommend upgrading to OpenClaw 2026.2.14 or later to mitigate the issue, with the fixing commit available at https://github.com/openclaw/openclaw/commit/013e8f6b3be3333a229a066eef26a45fec47ffcc. Further details on the vulnerability and remediation are provided in the GitHub Security Advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-jqpq-mgvm-f9r6 and the VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-command-hijacking-via-unsafe-path-handling.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-9934
Vulnerability Data
OpenClaw versions prior to 2026.2.14 contain a command hijacking vulnerability that allows attackers to execute unintended binaries by manipulating PATH environment variables through node-host execution or project-local bootstrapping. Attackers with authenticated access to node-host execution surfaces or those running OpenClaw…
more
in attacker-controlled directories can place malicious executables in PATH to override allowlisted safe-bin commands and achieve arbitrary command execution.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Establishes restrictive configuration settings that can define and lock down approved search paths.
Enforces approved authorizations so that only intended actors can place or modify elements in the search path.
Limits privileges so unintended actors cannot write to or control directories in the product's search path.
Restricts logical and physical access to change system configuration, including search-path settings and directories.
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.
Secure-development practices directly address design of search paths and resource loading.
Hardened configuration baselines can enforce safe search-path settings and reduce exposure.
Execution allow-listing can block malicious binaries placed in hijackable search locations.
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 detect uncontrolled search-path issues but does not prevent them by itself.
Restricting software installation reduces the chance that an attacker-controlled path element is introduced into the search path.
Secure system architecture and engineering principles require explicit control over search paths and resource locations.
Secure coding practices directly address the use of fixed or controlled search paths that can be influenced by unintended actors.
Configuration management can enforce approved search-path settings but does not inherently prevent the weakness.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248577 OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on symlinks. prevents CWE-427