EUVD-2026-21458Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
4Blast Radius
ecosystem impact- 5 npm packages depend on openclaw (5 direct, 0 indirect)
Ecosystem-wide dependent count for version 2026.3.22.
DescriptionCVE.org
OpenClaw before 2026.3.22 contains an authentication bypass vulnerability in the X-Forwarded-For header processing when trustedProxies is configured, allowing attackers to spoof loopback hops. Remote attackers can inject forged forwarding headers to bypass canvas authentication and rate-limiting protections by masquerading as loopback clients.
AnalysisAI
OpenClaw before version 2026.3.22 contains an authentication bypass vulnerability in X-Forwarded-For header processing when trustedProxies is configured, allowing unauthenticated remote attackers to spoof loopback client addresses and bypass canvas authentication and rate-limiting protections. The vulnerability exploits improper validation of forwarding headers to masquerade as local loopback connections, with a CVSS score of 6.5 reflecting moderate confidentiality and integrity impact but no direct availability impact.
Technical ContextAI
This vulnerability stems from improper trust handling in HTTP header parsing, specifically in the X-Forwarded-For (XFF) header mechanism used by reverse proxies and load balancers to communicate client originating IP addresses. When OpenClaw is configured with trustedProxies settings, it accepts XFF headers from specified proxy sources to determine the true client IP. The root cause (CWE-290: Improper Authentication) occurs because the application fails to properly validate that the loopback IP addresses in the forwarding chain are legitimate. Attackers can craft malicious X-Forwarded-For headers containing loopback addresses (127.0.0.1, ::1) that the vulnerable code incorrectly accepts as valid representations of local connections. This is particularly dangerous because loopback addresses typically receive special privileges in authentication and rate-limiting logic-they are often exempted or handled differently because they represent trusted internal services. The affected product is OpenClaw (CPE: cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) in all versions prior to 2026.3.22.
RemediationAI
Upgrade OpenClaw to version 2026.3.22 or later, which contains patches addressing the XFF header validation vulnerability. The fix is available via two upstream commits (630f1479c44f78484dfa21bb407cbe6f171dac87 and fc2d29ea926f47c428c556e92ec981441228d2a4) merged into the main repository. Until upgrading, operators should implement the following mitigations: (1) review and restrict the trustedProxies configuration to only explicitly trusted reverse proxy IP addresses rather than broad ranges, (2) ensure that loopback address filtering is enforced at the proxy layer to prevent injection of 127.0.0.1 or ::1 in X-Forwarded-For headers forwarded to the application, and (3) consider implementing additional rate-limiting or authentication validation independent of XFF header parsing. Consult the vendor advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-844j-xrrq-wgh4 and VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-xff-loopback-spoofing-bypass-in-canvas-authentication-and-rate-limiter for deployment-specific guidance.
Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.
Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b
OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att
An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.
OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e
Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in
OpenClaw sandbox browser functionality launches x11vnc for noVNC observer sessions without requiring authentication, all
OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director
OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func
OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste
OpenClaw versions prior to 2026.3.1 contain a sandbox escape vulnerability that allows authenticated attackers with low
OpenClaw versions 2026.1.30 and below fail to validate Telegram webhook secret tokens when `channels.telegram.webhookSec
Same weakness CWE-290 – Authentication Bypass by Spoofing
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today