<?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 19:59:45 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-CVE-2026-44994 — OpenClaw's Gateway Control UI bootstrap config required Gateway auth</title>
      <link>https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-44994</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;## Summary
Gateway Control UI bootstrap config required Gateway auth.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions
- Package: openclaw (npm)
- Affected versions: &amp;lt;= 2026.4.21
- Fixed version: 2026.4.22&lt;/p&gt;
&lt;p&gt;## Impact
When Gateway authentication was enabled, the Control UI bootstrap config endpoint could still be read without a valid Gateway token. That response could expose sensitive bootstrap/config fields intended only for authenticated Control UI sessions.&lt;/p&gt;
&lt;p&gt;## Fix
The bootstrap config route now goes through the same Gateway read-auth path as other authenticated Control UI reads. Regression tests cover unauthenticated rejection, valid-token access, and basePath handling.&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)
- 2321d67263bc710e357644d59f746b08d891051b&lt;/p&gt;
&lt;p&gt;## Verification
- The fix commit is contained in the public v2026.4.22 tag.
- openclaw@2026.4.22 is published on npm and the compiled package contains the fix.
- Focused regression coverage for this path passed before publication.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @zsxsoft 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;## Summary
Gateway Control UI bootstrap config required Gateway auth.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions
- Package: openclaw (npm)
- Affected versions: &amp;lt;= 2026.4.21
- Fixed version: 2026.4.22&lt;/p&gt;
&lt;p&gt;## Impact
When Gateway authentication was enabled, the Control UI bootstrap config endpoint could still be read without a valid Gateway token. That response could expose sensitive bootstrap/config fields intended only for authenticated Control UI sessions.&lt;/p&gt;
&lt;p&gt;## Fix
The bootstrap config route now goes through the same Gateway read-auth path as other authenticated Control UI reads. Regression tests cover unauthenticated rejection, valid-token access, and basePath handling.&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)
- 2321d67263bc710e357644d59f746b08d891051b&lt;/p&gt;
&lt;p&gt;## Verification
- The fix commit is contained in the public v2026.4.22 tag.
- openclaw@2026.4.22 is published on npm and the compiled package contains the fix.
- Focused regression coverage for this path passed before publication.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @zsxsoft for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-44994</guid>
    </item>
  </channel>
</rss>
