<?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-01T10:12:59.149147+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/cve-2026-22181</id>
    <title>CVE-2026-22181 — OpenClaw &lt; 2026.3.2 - DNS Pinning Bypass via Environment Proxy Configuration in web_fetch</title>
    <updated>2026-10-01T10:12:59.825407+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.3.2 contain a DNS pinning bypass vulnerability in strict URL fetch paths that allows attackers to circumvent SSRF guards when environment proxy variables are configured. When HTTP_PROXY, HTTPS_PROXY, or ALL_PROXY environment variables are present, attacker-influenced URLs can be routed through proxy behavior instead of pinned-destination routing, enabling access to internal targets reachable from the proxy environment.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-22181"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-8mvx-p2r9-r375</id>
    <title>GHSA-8mvx-p2r9-r375 — OpenClaw's web tools strict URL guard could lose DNS pinning when env proxy is configured</title>
    <updated>2026-10-01T10:12:59.825659+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>### Summary
`openclaw` web tools strict URL fetch paths could lose DNS pinning when environment proxy variables are configured (`HTTP_PROXY`/`HTTPS_PROXY`/`ALL_PROXY`, including lowercase variants).</p>
<p>In affected builds, strict URL checks (for example `web_fetch` and citation redirect resolution) validated one destination during SSRF guard checks, but runtime connection routing could proceed through an env-proxy dispatcher.</p>
<p>### Affected Packages / Versions
- Package: `openclaw` (npm)
- Vulnerable version range: `&lt;= 2026.3.1`
- Latest published npm version at triage time (2026-03-02): `2026.3.1`
- Patched versions: `&gt;= 2026.3.2` (released)</p>
<p>### Technical Details
The SSRF guard performed hostname resolution and policy checks, then selected a request dispatcher.</p>
<p>When env proxy settings were present, strict web-tool flows could use `EnvHttpProxyAgent` instead of the DNS-pinned dispatcher. This created a destination-binding gap between check-time resolution and connect-time routing.</p>
<p>The fix keeps DNS pinning on strict/untrusted web-tool URL paths and limits env-proxy bypass behavior to trusted/operator-controlled endpoints via an explicit dangerous opt-in.</p>
<p>### Impact
In deployments with env proxy variables configured, attacker-influenced URLs from web tools could be routed through proxy behavior instead of strict pinned-destination routing, which could allow access to internal/private targets reachable from that proxy environment.</p>
<p>### Mitigations
Before upgrading, operators c…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-8mvx-p2r9-r375"/>
  </entry>
</feed>
