CVE-2026-32015

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-03-19 22:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 10:34 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.1% in the next 30 days (EPSS).
• Severity: 7.3 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-03-19 22:16 UTC

Last modified

2026-06-17 10:34 UTC

Exploit probability

0.1% · EPSS, next 30 days

Weakness

CWE-426

Record status

Modified

Affected

• Openclaw < 2026.2.19

Attack profile CVSS 4.0 · 7.3

Attack vector

Local

Complexity

Low

Attack requirements

Present

Privileges needed

Low

User interaction

None

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-32015.md and follow it. Check whether this project is affected by CVE-2026-32015. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge