Which versions of Openclaw are affected by CVE-2026-32015?

OpenClaw gateway systems running versions 2026.1.21 through 2026.2.18 are vulnerable to privilege escalation attacks where threat actors can execute malicious code by manipulating process PATH…. A patch is available.

How to fix or mitigate CVE-2026-32015?

Within 24 hours: Inventory all OpenClaw deployments and identify systems running vulnerable versions 2026.1.21-2026.2.18; immediately restrict gateway process execution privileges and isolate affected systems from production traffic where possible. Within 7 days: Implement PATH environment variable hardening on all gateway servers by removing user-writable directories and enforcing absolute binary paths; enable enhanced logging and monitoring of process execution. Within 30 days: Upgrade to OpenClaw 2026.2.19 or later when patch becomes available; conduct forensic review of gateway audit logs for indicators of exploitation.

Openclaw CVE-2026-32015

Q: What is the CVSS score of CVE-2026-32015?

CVE-2026-32015 has a CVSS 4.0 base score of 7.3 (High). CVSS 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:X. EPSS exploitation probability: 0.0%.

HIGH

Untrusted Search Path (CWE-426)

2026-03-19 disclosure@vulncheck.com

GHSA-g75x-8qqm-2vxp

Authentication Bypass Openclaw

7.3

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

7.3 HIGH

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:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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:X

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

Analysis Generated

Mar 19, 2026 - 22:30 vuln.today

CVE Published

Mar 19, 2026 - 22:16 nvd

HIGH 7.3

DescriptionCVE.org

OpenClaw versions 2026.1.21 prior to 2026.2.19 contain a path hijacking vulnerability in tools.exec.safeBins that allows attackers to bypass allowlist checks by controlling process PATH resolution. Attackers who can influence the gateway process PATH or launch environment can execute trojan binaries with allowlisted names, such as jq, circumventing executable validation controls.

AnalysisAI

OpenClaw versions before 2026.2.19 contain a path hijacking vulnerability in tools.exec.safeBins that allows local attackers with process environment control to execute arbitrary binaries by spoofing allowlisted tool names like jq. An attacker who can manipulate the gateway process PATH can bypass executable validation controls and achieve code execution with the privileges of the affected process. No patch is currently available.

Technical ContextAI

The vulnerability stems from improper path resolution (CWE-426: Untrusted Search Path) in OpenClaw's executable validation mechanism. The tools.exec.safeBins component maintains an allowlist of trusted executables but fails to use absolute paths when invoking them, instead relying on PATH resolution. This allows an attacker who can modify the PATH environment variable or place malicious executables in directories searched before legitimate binaries to execute arbitrary code while appearing to run allowlisted programs. The affected product is identified as OpenClaw, an open-source platform, with versions 2026.1.21 through 2026.2.18 vulnerable to this attack.

RemediationAI

Upgrade OpenClaw to version 2026.2.19 or later, which contains the fix implemented in commit 28bac46c92069dc728524fbf383024c1b64e5c23 (https://github.com/openclaw/openclaw/commit/28bac46c92069dc728524fbf383024c1b64e5c23). As a temporary mitigation, restrict access to the gateway process environment, ensure PATH variables are properly sanitized and controlled, and consider implementing additional access controls around the OpenClaw gateway service. Monitor for unexpected process executions or PATH modifications in OpenClaw environments until patching is complete.