<?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://db.gcve.eu</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>Tue, 29 Sep 2026 00:45:43 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-CVE-2026-28468 — OpenClaw has an authentication bypass in sandbox browser bridge server</title>
      <link>https://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-28468</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;openclaw could start the sandbox browser bridge server without authentication.&lt;/p&gt;
&lt;p&gt;When the sandboxed browser is enabled, openclaw runs a local (loopback) HTTP bridge that exposes browser control endpoints (for example `/profiles`, `/tabs`, `/tabs/open`, `/agent/*`). Due to missing auth wiring in the sandbox initialization path, that bridge server accepted requests without requiring gateway auth.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;A local attacker (any process on the same machine) could access the bridge server port and:&lt;/p&gt;
&lt;p&gt;- enumerate open tabs and retrieve CDP WebSocket URLs
- open/close/navigate tabs
- execute JavaScript in page contexts via CDP
- exfiltrate cookies/session data and page contents from authenticated sessions&lt;/p&gt;
&lt;p&gt;This is a localhost-only exposure (CVSS AV:L), but provides full browser-session compromise for sandboxed browser usage.&lt;/p&gt;
&lt;p&gt;## Affected Versions&lt;/p&gt;
&lt;p&gt;- Introduced in: `2026.1.29-beta.1` (first npm release that shipped the sandbox browser bridge)
- Affected range: `&amp;gt;=2026.1.29-beta.1 &amp;lt;2026.2.14`&lt;/p&gt;
&lt;p&gt;## Patched Versions&lt;/p&gt;
&lt;p&gt;- `2026.2.14`&lt;/p&gt;
&lt;p&gt;## Mitigation&lt;/p&gt;
&lt;p&gt;- Upgrade to `2026.2.14` (recommended).
- Or disable the sandboxed browser (`agents.defaults.sandbox.browser.enabled=false`).&lt;/p&gt;
&lt;p&gt;## Fix Details&lt;/p&gt;
&lt;p&gt;- The sandbox browser bridge server now always requires auth and enforces the same gateway browser control auth (token/password) that loopback browser clients already use.
- Additional hardening: bridge server refuses non-loopback binds; local helper servers are bound to loopback.
- Added re…&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;## Summary&lt;/p&gt;
&lt;p&gt;openclaw could start the sandbox browser bridge server without authentication.&lt;/p&gt;
&lt;p&gt;When the sandboxed browser is enabled, openclaw runs a local (loopback) HTTP bridge that exposes browser control endpoints (for example `/profiles`, `/tabs`, `/tabs/open`, `/agent/*`). Due to missing auth wiring in the sandbox initialization path, that bridge server accepted requests without requiring gateway auth.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;A local attacker (any process on the same machine) could access the bridge server port and:&lt;/p&gt;
&lt;p&gt;- enumerate open tabs and retrieve CDP WebSocket URLs
- open/close/navigate tabs
- execute JavaScript in page contexts via CDP
- exfiltrate cookies/session data and page contents from authenticated sessions&lt;/p&gt;
&lt;p&gt;This is a localhost-only exposure (CVSS AV:L), but provides full browser-session compromise for sandboxed browser usage.&lt;/p&gt;
&lt;p&gt;## Affected Versions&lt;/p&gt;
&lt;p&gt;- Introduced in: `2026.1.29-beta.1` (first npm release that shipped the sandbox browser bridge)
- Affected range: `&amp;gt;=2026.1.29-beta.1 &amp;lt;2026.2.14`&lt;/p&gt;
&lt;p&gt;## Patched Versions&lt;/p&gt;
&lt;p&gt;- `2026.2.14`&lt;/p&gt;
&lt;p&gt;## Mitigation&lt;/p&gt;
&lt;p&gt;- Upgrade to `2026.2.14` (recommended).
- Or disable the sandboxed browser (`agents.defaults.sandbox.browser.enabled=false`).&lt;/p&gt;
&lt;p&gt;## Fix Details&lt;/p&gt;
&lt;p&gt;- The sandbox browser bridge server now always requires auth and enforces the same gateway browser control auth (token/password) that loopback browser clients already use.
- Additional hardening: bridge server refuses non-loopback binds; local helper servers are bound to loopback.
- Added re…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-28468</guid>
    </item>
    <item>
      <title>CVE-2026-28468 — OpenClaw 2026.1.29-beta.1 &lt; 2026.2.14 - Authentication Bypass in Sandbox Browser Bridge Server</title>
      <link>https://db.gcve.eu/vuln/cve-2026-28468</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenClaw&lt;/p&gt;
&lt;p&gt;OpenClaw versions 2026.1.29-beta.1 prior to 2026.2.14 contain a vulnerability in the sandbox browser bridge server in which it accepts requests without requiring gateway authentication, allowing local attackers to access browser control endpoints. A local attacker can enumerate tabs, retrieve WebSocket URLs, execute JavaScript, and exfiltrate cookies and session data from authenticated browser contexts.&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 2026.1.29-beta.1 prior to 2026.2.14 contain a vulnerability in the sandbox browser bridge server in which it accepts requests without requiring gateway authentication, allowing local attackers to access browser control endpoints. A local attacker can enumerate tabs, retrieve WebSocket URLs, execute JavaScript, and exfiltrate cookies and session data from authenticated browser contexts.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-28468</guid>
    </item>
  </channel>
</rss>
