OpenClaw
OpenClaw: Untrusted web origins can obtain authenticated operator.admin access in trusted-proxy mode
OpenClaw is a personal AI assistant. Prior to 2026.3.11, browser-originated WebSocket connections could bypass origin validation when gateway.auth.mode was set to trusted-proxy and the request arrived with proxy headers. A page served from an untrusted origin could connect through a trusted reverse proxy, inherit proxy-authenticated identity, and establish a privileged operator session. This vulnerability is fixed in 2026.3.11.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2026.3.11
Fixed in 2026.3.11
Mitigation
Upgrade openclaw to 2026.3.11 or later.
References
- Vendor advisory github.com/openclaw/openclaw/security/advisori…
- Patch github.com/openclaw/openclaw/commit/ebed3bbde1…
- Release notes github.com/openclaw/openclaw/releases/tag/v202…
Timeline
Days relative to CVE publicationFirst public PoC 4.9 days after publication; not in CISA KEV. First PoC: NULL200OK/OpenClaw-Indirect-Prompt-Injection (created 17 Mar 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| NULL200OK/OpenClaw-Indirect-Prompt-Injection | 17 Mar 2026 +4.9 d | 2 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.