<?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://cve.radiocsirt.org</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>Thu, 15 Oct 2026 00:41:49 +0000</lastBuildDate>
    <item>
      <title>GHSA-pfv7-rr5m-qmv6 — OpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pfv7-rr5m-qmv6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When the optional Chrome extension relay is enabled, `/extension` accepted unauthenticated WebSocket upgrades while `/json/*` and `/cdp` required auth.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Affected: `&amp;lt;= 2026.2.17`
- Latest published npm version at triage time: `2026.2.17`&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This is a local-only issue on loopback (`127.0.0.1`) and only applies when the extension relay feature is in use. A local process on the same machine could connect to `/extension` without the token and interfere with extension-relay behavior.&lt;/p&gt;
&lt;p&gt;No remote network exploit path is involved.&lt;/p&gt;
&lt;p&gt;### Fix&lt;/p&gt;
&lt;p&gt;- Require gateway-token auth on both `/extension` and `/cdp` relay WebSocket endpoints.
- Keep loopback/origin checks as defense-in-depth, not as authentication.
- Use one token path in setup: `gateway.auth.token` / `OPENCLAW_GATEWAY_TOKEN`.&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)&lt;/p&gt;
&lt;p&gt;- `7e54b6c96feb1a5c30884f2b32037b8dadd0e532`&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @tdjackey for reporting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When the optional Chrome extension relay is enabled, `/extension` accepted unauthenticated WebSocket upgrades while `/json/*` and `/cdp` required auth.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Affected: `&amp;lt;= 2026.2.17`
- Latest published npm version at triage time: `2026.2.17`&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This is a local-only issue on loopback (`127.0.0.1`) and only applies when the extension relay feature is in use. A local process on the same machine could connect to `/extension` without the token and interfere with extension-relay behavior.&lt;/p&gt;
&lt;p&gt;No remote network exploit path is involved.&lt;/p&gt;
&lt;p&gt;### Fix&lt;/p&gt;
&lt;p&gt;- Require gateway-token auth on both `/extension` and `/cdp` relay WebSocket endpoints.
- Keep loopback/origin checks as defense-in-depth, not as authentication.
- Use one token path in setup: `gateway.auth.token` / `OPENCLAW_GATEWAY_TOKEN`.&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)&lt;/p&gt;
&lt;p&gt;- `7e54b6c96feb1a5c30884f2b32037b8dadd0e532`&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @tdjackey for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pfv7-rr5m-qmv6</guid>
    </item>
  </channel>
</rss>
