CVE-2026-44995: OpenClaw · MCP stdio server env could load dangerous startup variables from workspace config
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 5.4 Medium : upgrade to 2026.4.20 when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.4.20
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 11 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.4.20.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in OpenClaw version 2026.4.20 that filters unsafe environment variables before spawning MCP stdio servers. Operators should upgrade to version 2026.4.20 or later to remediate this vulnerability.
Description
OpenClaw CLI versions before 2026.4.20 contain a vulnerability where the MCP stdio server environment can load dangerous startup variables from workspace configuration. This allows malicious workspaces to pass harmful environment variables like NODE_OPTIONS, LD_PRELOAD, or BASH_ENV to the MCP server process, potentially causing it to load attacker-controlled code. The risk is limited to local or workspace trust boundaries and requires the operator to run OpenClaw in a maliciously configured workspace. The issue is fixed in version 2026.4.20 by filtering unsafe environment variables before spawning MCP servers.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-mj59-h3q9-ghfh (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-44995 (opens in a new tab)
- github.com/openclaw/openclaw/commit/62fa5071896e95edc7f67d1cebc70a2859e283af (opens in a new tab)
- github.com/openclaw/openclaw/commit/85d86ebc4bf3d2226d39d132a484f4f7a299fa1b (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- vulncheck.com/advisories/openclaw-arbitrary-code-execution-via-mcp-stdio-environment-variables (opens in a new tab)