Skip to main content
VulnerabilityPublished Updated

CVE-2026-41370: OpenClaw · Path traversal via inbound channel attachment path in ACP dispatch allows arbitrary file read

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2026.3.31 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.31
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 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 16 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

Users should upgrade OpenClaw CLI to version 2026.3.31 or later, where the path traversal vulnerability has been fixed by enforcing root directory checks on attachment paths. No other mitigation is required as the fix is officially released.

Description

OpenClaw CLI versions up to 2026.3.28 contain a path traversal vulnerability in the ACP dispatch component that allows reading arbitrary files outside intended directories. This issue arises because the attachment path is not properly restricted, enabling access beyond the guarded attachment-cache or root directories. The vulnerability is fixed in version 2026.3.31 and later.

References

Community reviews

Loading reviews…