https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 20:00:40 +0000 https://vulnerability.circl.lu/vuln/cve-2026-41916 <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> <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> https://vulnerability.circl.lu/vuln/cve-2026-41916 https://vulnerability.circl.lu/vuln/ghsa-68x5-xx89-w9mm <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> <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> https://vulnerability.circl.lu/vuln/ghsa-68x5-xx89-w9mm