OpenClaw before 2026.3.31 contains an authentication boundary vulnerability where Telegram legacy allowFrom migration incorrectly fans default-account trust into all named accounts. Attackers can exploit this trust propagation to bypass authentication controls and gain unauthorized access to named accounts.
References
Configurations
History
28 Apr 2026, 18:56
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/openclaw/openclaw/commit/d8c68c8d4265ea6fa5e8c5e056534c351bddef37 - Patch | |
| References | () https://github.com/openclaw/openclaw/security/advisories/GHSA-f693-58pc-2gfr - Vendor Advisory | |
| References | () https://www.vulncheck.com/advisories/openclaw-authentication-boundary-bypass-via-telegram-legacy-allowfrom-migration - Third Party Advisory | |
| CPE | cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:* | |
| First Time |
Openclaw openclaw
Openclaw |
23 Apr 2026, 22:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-04-23 22:16
Updated : 2026-04-28 18:56
NVD link : CVE-2026-41340
Mitre link : CVE-2026-41340
CVE.ORG link : CVE-2026-41340
JSON object : View
Products Affected
openclaw
- openclaw
CWE
CWE-372
Incomplete Internal State Distinction
