https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-10-03T18:13:32.183016+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/cve-2026-26324 CVE-2026-26324 — OpenClaw has a SSRF guard bypass via full-form IPv4-mapped IPv6 (loopback / metadata reachable) 2026-10-03T18:13:32.549516+00:00

Affected: openclaw

OpenClaw is a personal AI assistant. Prior to version 2026.2.14, OpenClaw's SSRF protection could be bypassed using full-form IPv4-mapped IPv6 literals such as `0:0:0:0:0:ffff:7f00:1` (which is `127.0.0.1`). This could allow requests that should be blocked (loopback / private network / link-local metadata) to pass the SSRF guard. Version 2026.2.14 patches the issue.

 https://vulnerability.circl.lu/vuln/ghsa-jrvc-8ff5-2f9f GHSA-jrvc-8ff5-2f9f — OpenClaw has a SSRF guard bypass via full-form IPv4-mapped IPv6 (loopback / metadata reachable) 2026-10-03T18:13:32.549644+00:00

Affected: npm: openclaw

### Summary

OpenClaw's SSRF protection could be bypassed using full-form IPv4-mapped IPv6 literals such as `0:0:0:0:0:ffff:7f00:1` (which is `127.0.0.1`). This could allow requests that should be blocked (loopback / private network / link-local metadata) to pass the SSRF guard.

- Vulnerable component: SSRF guard (`src/infra/net/ssrf.ts`) - Issue type: SSRF protection bypass

### Affected Packages / Versions

- Package: `openclaw` (npm) - Vulnerable: `<= 2026.2.13` - Patched: `>= 2026.2.14` (planned next release)

### Details

The SSRF guard's IP classification did not consistently detect private IPv4 addresses when they were embedded in IPv6 using full-form IPv4-mapped IPv6 notation. As a result, inputs like `0:0:0:0:0:ffff:7f00:1` could bypass loopback/private network blocking.

### Fix Commit(s)

- `c0c0e0f9aecb913e738742f73e091f2f72d39a19`

### Release Process Note

This advisory is kept in draft state with the patched version set to the planned next release. Once `openclaw@2026.2.14` is published to npm, the only remaining step should be to publish this advisory.

Thanks @yueyueL for reporting.