<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Oct 2026 16:14:30 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-GHSA-5847-rm3g-23mw — OpenClaw has hook auth rate limiter bypass via IPv4-mapped IPv6 client key variants</title>
      <link>https://vulnerability.circl.lu/vuln/brew-openclaw-cli-ghsa-5847-rm3g-23mw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;## Vulnerability&lt;/p&gt;
&lt;p&gt;The hook authentication throttle keyed failed attempts by raw socket `remoteAddress` text.&lt;/p&gt;
&lt;p&gt;IPv4 and IPv4-mapped IPv6 forms of the same client (for example `1.2.3.4` and `::ffff:1.2.3.4`) were treated as different clients, allowing separate rate-limit buckets.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker could split failed hook-auth attempts across both address forms and effectively double the brute-force budget from 20 to 40 attempts per 60-second window.&lt;/p&gt;
&lt;p&gt;## Affected Components&lt;/p&gt;
&lt;p&gt;- `src/gateway/server-http.ts`
- `src/gateway/auth-rate-limit.ts`&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Vulnerable versions: `&amp;lt;= 2026.2.21-2`
- Patched version (planned next release): `2026.2.22`&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;Centralize and reuse canonical client-IP normalization for auth rate-limiting, and use that canonical key for hook auth throttling.&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)&lt;/p&gt;
&lt;p&gt;- `3284d2eb227e7b6536d543bcf5c3e320bc9d13c5`&lt;/p&gt;
&lt;p&gt;## Release Process Note&lt;/p&gt;
&lt;p&gt;`patched_versions` is pre-set to the planned next release (`2026.2.22`) so once npm release `2026.2.22` is published, this advisory can be published directly.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @aether-ai-agent for reporting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;## Vulnerability&lt;/p&gt;
&lt;p&gt;The hook authentication throttle keyed failed attempts by raw socket `remoteAddress` text.&lt;/p&gt;
&lt;p&gt;IPv4 and IPv4-mapped IPv6 forms of the same client (for example `1.2.3.4` and `::ffff:1.2.3.4`) were treated as different clients, allowing separate rate-limit buckets.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker could split failed hook-auth attempts across both address forms and effectively double the brute-force budget from 20 to 40 attempts per 60-second window.&lt;/p&gt;
&lt;p&gt;## Affected Components&lt;/p&gt;
&lt;p&gt;- `src/gateway/server-http.ts`
- `src/gateway/auth-rate-limit.ts`&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Vulnerable versions: `&amp;lt;= 2026.2.21-2`
- Patched version (planned next release): `2026.2.22`&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;Centralize and reuse canonical client-IP normalization for auth rate-limiting, and use that canonical key for hook auth throttling.&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)&lt;/p&gt;
&lt;p&gt;- `3284d2eb227e7b6536d543bcf5c3e320bc9d13c5`&lt;/p&gt;
&lt;p&gt;## Release Process Note&lt;/p&gt;
&lt;p&gt;`patched_versions` is pre-set to the planned next release (`2026.2.22`) so once npm release `2026.2.22` is published, this advisory can be published directly.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @aether-ai-agent for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/brew-openclaw-cli-ghsa-5847-rm3g-23mw</guid>
    </item>
  </channel>
</rss>
