GitHub Advisoryadvisory · npm

GHSA-68x5-xx89-w9mm OpenClaw: resolvedAuth closure becomes stale after config reload

MEDIUM Published 2026-04-09 Modified 2026-04-28 Official page ↗
Aliases
CVE-2026-41916
Ecosystem
npm
Packages
openclaw
Severity
Moderate
CVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Weaknesses
CWE-613
Reviewed
2026-04-09

Affected packages

• npm openclaw: < 2026.4.8 → fixed in 2026.4.8

Description

Impact resolvedAuth closure becomes stale after config reload. After a config reload, newly accepted gateway connections could continue using stale resolved auth state. 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. Affected Packages / Versions • Package: `openclaw` (npm) • Affected versions: `<= 2026.4.1` • Patched versions: `2026.4.8` Fix The issue was fixed on `main` and is available in the patched npm version listed above. The verified fixed tree is commit `d7c3210cd6f5fdfdc1beff4c9541673e814354d5`. Verification The fix was re-checked against `main` before publication, including targeted regression tests for the affected security boundary. Credits Thanks @kexinoh of Tencent zhuque Lab (https://github.com/Tencent/AI-Infra-Guard) for reporting.

Related

Weakness · not in database (1)

Alias · CVE (1)

  • CVE-2026-41916 OpenClaw before 2026.4.8 contains an authentication state management vulnerability where the resolvedAuth closure becomes stale after… vulnerability

References