Local code execution via trusted-prefix shell fallback
Published Mar 18, 2026 · Updated Mar 18, 2026
Code execution in OpenClaw 2026.2.22 through 2026.2.22-2 allows local users to run attacker-controlled binaries through SHELL. The shell-env fallback accepts any executable beneath hardcoded trusted prefixes and launches it as a login shell to collect environment data. Exploitation requires influence over the process SHELL value and write access to a trusted-prefix directory, and the binary runs in the OpenClaw process context.
Summary
What happened
Code execution in OpenClaw 2026.2.22 through 2026.2.22-2 allows local users to run attacker-controlled binaries through SHELL. The shell-env fallback accepts any executable beneath hardcoded trusted prefixes and launches it as a login shell to collect environment data. Exploitation requires influence over the process SHELL value and write access to a trusted-prefix directory, and the binary runs in the OpenClaw process context.
The record
- CVE
- CVE-2026-22217
- Published
- Mar 18, 2026
- Updated
- Mar 18, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-829, T1059.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 18, 2026CVE publishedPublication date reported by the CVE source.
- Mar 18, 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=2026.2.22 <2026.2.23
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