Code execution via unfiltered MCP stdio environment
Published May 11, 2026 · Updated May 11, 2026
Code injection in OpenClaw before 2026.4.20 allows local users to execute arbitrary code through malicious MCP stdio configuration. resolveStdioMcpServerLaunchConfig passed the workspace-supplied env object to child processes without filtering startup variables such as NODE_OPTIONS, LD_PRELOAD, or BASH_ENV. Execution requires an operator to open the malicious workspace and start a session that uses the configured MCP server.
Summary
What happened
Code injection in OpenClaw before 2026.4.20 allows local users to execute arbitrary code through malicious MCP stdio configuration. resolveStdioMcpServerLaunchConfig passed the workspace-supplied env object to child processes without filtering startup variables such as NODE_OPTIONS, LD_PRELOAD, or BASH_ENV. Execution requires an operator to open the malicious workspace and start a session that uses the configured MCP server.
The record
- CVE
- CVE-2026-44995
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-829, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 11, 2026CVE publishedPublication date reported by the CVE source.
- May 11, 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.4.20
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