<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T12:33:39.797836+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-32019</id>
    <title>BREW-openclaw-cli-CVE-2026-32019 — OpenClaw has incomplete IPv4 special-use SSRF blocking in web fetch guard</title>
    <updated>2026-10-02T12:33:39.800043+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>### Summary
`isPrivateIpv4()` in bundled SSRF guard code missed several IPv4 special-use/non-global ranges, so `web_fetch` could allow targets that should be blocked by SSRF policy.</p>
<p>### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published affected version: `2026.2.21-2` (published 2026-02-21)
- Structured vulnerable range: `&lt;= 2026.2.21-2`
- Planned patched version (pre-set): `&gt;= 2026.2.22`</p>
<p>### Impact
Low severity. Exploitation requires network reachability to the relevant special-use ranges and a request path that reaches `web_fetch` URL fetching.</p>
<p>### Technical Details
Affected releases used narrow IPv4 private-range checks that omitted multiple RFC special-use/non-global ranges. This allowed requests such as `http://198.18.0.1/...` through SSRF validation in affected releases. Follow-up hardening consolidates local-host/tailnet range checks so gateway/browser/tailnet paths share one canonical IP classification flow.</p>
<p>### Fix Commit(s)
- `71bd15bb4294d3d1b54386064d69cd0f5f731bd8`
- `44dfbd23df453e51b71ef79a148c28c53e89168c`
- `333fbb86347998526dd514290adfd5f727caa6d9`
- `f14ebd743cfc73f667fae80af70043d0ab1f88bd`</p>
<p>OpenClaw thanks @princeeismond-dot for reporting.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-32019"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-32019</id>
    <title>CVE-2026-32019 — OpenClaw &lt; 2026.2.22 - Incomplete IPv4 Special-Use Range Blocking in SSRF Guard</title>
    <updated>2026-10-02T12:33:39.800143+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> OpenClaw</p>
<p>OpenClaw versions prior to 2026.2.22 contain incomplete IPv4 special-use range validation in the isPrivateIpv4() function, allowing requests to RFC-reserved ranges to bypass SSRF policy checks. Attackers with network reachability to special-use IPv4 ranges can exploit web_fetch functionality to access blocked addresses such as 198.18.0.0/15 and other non-global ranges.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-32019"/>
  </entry>
</feed>
