<?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, 03 Oct 2026 03:47:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-22174 — OpenClaw &lt; 2026.2.22 - Gateway Token Disclosure via Chrome CDP Probe</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-22174</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenClaw&lt;/p&gt;
&lt;p&gt;OpenClaw versions prior to 2026.2.22 inject the x-OpenClaw-relay-token header into Chrome CDP probe traffic on loopback interfaces, allowing local processes to capture the Gateway authentication token. An attacker controlling a loopback port can intercept CDP reachability probes to the /json/version endpoint and reuse the leaked token as Gateway bearer authentication.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenClaw&lt;/p&gt;
&lt;p&gt;OpenClaw versions prior to 2026.2.22 inject the x-OpenClaw-relay-token header into Chrome CDP probe traffic on loopback interfaces, allowing local processes to capture the Gateway authentication token. An attacker controlling a loopback port can intercept CDP reachability probes to the /json/version endpoint and reuse the leaked token as Gateway bearer authentication.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-22174</guid>
    </item>
    <item>
      <title>GHSA-v3j7-34xh-6g3w — OpenClaw Loopback CDP probe can leak Gateway token to local listener</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-v3j7-34xh-6g3w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary
A local process can capture the OpenClaw Gateway auth token from Chrome CDP probe traffic on loopback.&lt;/p&gt;
&lt;p&gt;### Details
Affected versions inject `x-openclaw-relay-token` for loopback CDP URLs, and CDP reachability probes send that header to `/json/version`.
If an attacker controls the probed loopback port, they can read that token and reuse it as Gateway bearer auth.&lt;/p&gt;
&lt;p&gt;Relevant code paths (pre-fix):
- `src/browser/extension-relay.ts` (`getChromeExtensionRelayAuthHeaders`)
- `src/browser/cdp.helpers.ts` (`getHeadersWithAuth`)
- `src/browser/chrome.ts` (`fetchChromeVersion`)&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published (at triage): `2026.2.21-2`
- Vulnerable: `&amp;lt;= 2026.2.21-2`
- Patched: &amp;gt;= 2026.2.22&lt;/p&gt;
&lt;p&gt;### Deployment Model Applicability
This does **not** change OpenClaw’s documented security model for standard single-owner installs (you own the machine/VPS and trust local processes under that OS account boundary).
Risk is for **non-standard shared-user/shared-host installs** where an untrusted local user/process can race/bind the loopback relay port.&lt;/p&gt;
&lt;p&gt;### Impact
- Local credential disclosure.
- Follow-on impact depends on local deployment and enabled Gateway capabilities.&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `afa22acc4a09fdf32be8a167ae216bee85c30dad`&lt;/p&gt;
&lt;p&gt;### Release Process Note
Patched version is set to &amp;gt;= 2026.2.22 for the published release.&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
A local process can capture the OpenClaw Gateway auth token from Chrome CDP probe traffic on loopback.&lt;/p&gt;
&lt;p&gt;### Details
Affected versions inject `x-openclaw-relay-token` for loopback CDP URLs, and CDP reachability probes send that header to `/json/version`.
If an attacker controls the probed loopback port, they can read that token and reuse it as Gateway bearer auth.&lt;/p&gt;
&lt;p&gt;Relevant code paths (pre-fix):
- `src/browser/extension-relay.ts` (`getChromeExtensionRelayAuthHeaders`)
- `src/browser/cdp.helpers.ts` (`getHeadersWithAuth`)
- `src/browser/chrome.ts` (`fetchChromeVersion`)&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published (at triage): `2026.2.21-2`
- Vulnerable: `&amp;lt;= 2026.2.21-2`
- Patched: &amp;gt;= 2026.2.22&lt;/p&gt;
&lt;p&gt;### Deployment Model Applicability
This does **not** change OpenClaw’s documented security model for standard single-owner installs (you own the machine/VPS and trust local processes under that OS account boundary).
Risk is for **non-standard shared-user/shared-host installs** where an untrusted local user/process can race/bind the loopback relay port.&lt;/p&gt;
&lt;p&gt;### Impact
- Local credential disclosure.
- Follow-on impact depends on local deployment and enabled Gateway capabilities.&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `afa22acc4a09fdf32be8a167ae216bee85c30dad`&lt;/p&gt;
&lt;p&gt;### Release Process Note
Patched version is set to &amp;gt;= 2026.2.22 for the published release.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @tdjackey for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-v3j7-34xh-6g3w</guid>
    </item>
  </channel>
</rss>
