Code execution via unbound script approval
Published Mar 29, 2026 · Updated Mar 29, 2026
Approval bypass in OpenClaw before 2026.3.11 allows local users to execute rewritten scripts as the OpenClaw runtime user. The node-host system.run approval flow accepts interpreter and runtime forms without binding exactly one concrete script file, allowing its contents to change after approval. Exploitation requires approval mode, a low-privileged actor able to replace the local script, and user interaction; resulting code runs with the runtime user's access.
Summary
What happened
Approval bypass in OpenClaw before 2026.3.11 allows local users to execute rewritten scripts as the OpenClaw runtime user. The node-host system.run approval flow accepts interpreter and runtime forms without binding exactly one concrete script file, allowing its contents to change after approval. Exploitation requires approval mode, a low-privileged actor able to replace the local script, and user interaction; resulting code runs with the runtime user's access.
The record
- CVE
- CVE-2026-32979
- Published
- Mar 29, 2026
- Updated
- Mar 29, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-367, T1059
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 29, 2026CVE publishedPublication date reported by the CVE source.
- Mar 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.3.11
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo