Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.

OpenClaw users: unauthorized code can run after approval

published 7 months ago

Summary

OpenClaw versions before 2026.3.1 have a security weakness that lets attackers change what program runs after approval, potentially allowing them to run any code they want. This is a serious issue that can be exploited by hackers. It's recommended to update to version 2026.3.1 or later to fix this vulnerability.

What to do

Update steipete openclaw to version 2026.3.1 or later.

Affected software

Ecosystem	Vendor	Product	Affected versions
npm	steipete	openclaw	< 2026.3.1

Original advisory text

Duplicate Advisory: OpenClaw: system.run approvals did not bind PATH-token executable identity, enabling post-approval executable rebind

## Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-q399-23r3-hfx4. This link is maintained to preserve external references.

## Original Description
OpenClaw versions prior to 2026.3.1 fail to pin executable identity for non-path-like argv[0] tokens in system.run approvals, allowing post-approval executable rebind attacks. Attackers can modify PATH resolution after approval to execute a different binary than the operator approved, enabling arbitrary command execution.

References

Fix within

Internet-facing 60 days

Internal At next upgrade

Not known to be exploited
Needs hands-on effort to exploit (estimated)
Gives an attacker partial control (estimated)

Severity

4.4 Medium

Type

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition

Timeline

Published19 Mar 2026

Updated19 Mar 2026

First seen19 Mar 2026

Sources

GHSA-q86m-697p-h7fh · GHSA

Track software like this

Free during beta