<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T19:42:11.471788+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-41916</id>
    <title>CVE-2026-41916 — OpenClaw &lt; 2026.4.8 - Stale Authentication State via Config Reload</title>
    <updated>2026-09-28T19:42:11.506005+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> OpenClaw</p>
<p>OpenClaw before 2026.4.8 contains an authentication state management vulnerability where the resolvedAuth closure becomes stale after configuration reload. Newly accepted gateway connections continue using outdated resolved auth state, allowing attackers to bypass authentication controls through config reload operations.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-41916"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-68x5-xx89-w9mm</id>
    <title>GHSA-68x5-xx89-w9mm — OpenClaw: resolvedAuth closure becomes stale after config reload</title>
    <updated>2026-09-28T19:42:11.506154+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>## Impact</p>
<p>resolvedAuth closure becomes stale after config reload.</p>
<p>After a config reload, newly accepted gateway connections could continue using stale resolved auth state.</p>
<p>OpenClaw is a user-controlled local assistant. This advisory is scoped to the OpenClaw trust model and does not assume a multi-tenant service boundary.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Affected versions: `&lt;= 2026.4.1`
- Patched versions: `2026.4.8`</p>
<p>## Fix</p>
<p>The issue was fixed on `main` and is available in the patched npm version listed above. The verified fixed tree is commit `d7c3210cd6f5fdfdc1beff4c9541673e814354d5`.</p>
<p>## Verification</p>
<p>The fix was re-checked against `main` before publication, including targeted regression tests for the affected security boundary.</p>
<p>## Credits</p>
<p>Thanks @kexinoh of Tencent zhuque Lab (https://github.com/Tencent/AI-Infra-Guard) for reporting.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-68x5-xx89-w9mm"/>
  </entry>
</feed>
