Skip to main content
CVE-2026-26324VulnerabilityPublished Updated

Openclaw cli: OpenClaw has a SSRF guard bypass via full-form IPv4-mapped IPv6 (loopback / metadata reachable)

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2026.2.14 soon.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.2.14
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A: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 18 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.2.14.

Affected software

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

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 and planned for release in openclaw CLI version 2026.2.14. Users should upgrade to version 2026.2.14 or later once published to mitigate this SSRF bypass vulnerability.

Description

OpenClaw CLI versions before 2026.2.14 have a Server-Side Request Forgery (SSRF) protection bypass vulnerability. The SSRF guard fails to block requests using full-form IPv4-mapped IPv6 addresses such as 0:0:0:0:0:ffff:7f00:1, which maps to the loopback address 127.0.0.1. This allows potentially unauthorized access to loopback, private network, or link-local metadata endpoints. The issue is fixed in version 2026.2.14.

References

Community reviews

Loading reviews…