Skip to main content
VulnerabilityPublished Updated

CVE-2026-41357: OpenClaw · SSH-based sandbox backends pass unsanitized process.env to child processes

Affects openclaw-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-41357· Low 2.0

Not known to be exploited · CVSS 2.0 Low : upgrade to 2026.3.31 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
2.0Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.02.0
CNA (VulnCheck)CVSS 3.13.3
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.31
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.31.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.3.31
Fixed in
  • 2026.3.31

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade OpenClaw CLI to version 2026.3.31 or later, which contains the official fix. No additional mitigation is required as the patch fully addresses the vulnerability.

Description

OpenClaw CLI versions prior to 2026.3.31 have a vulnerability where SSH-based sandbox backends pass unsanitized environment variables (process.env) to child processes. This can lead to local environment variable leakage in SSH child processes. Remote leakage requires non-default SSH environment forwarding, which is not common, so the severity is considered low. The issue is fixed in version 2026.3.31.

References

Community reviews

Loading reviews…