CVE-2026-41299: OpenClaw · Reliance on Untrusted Inputs in a Security Decision
Affects OpenClawSource GCVE Database
Not known to be exploited · CVSS 7.1 High : upgrade to 2026.3.28 soon.
Data as of 12 Nov 2026, 01:19 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.1 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.1 |
- Patch
- Available – fixed in 2026.3.28
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade OpenClaw to 2026.3.28.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenClaw OpenClaw | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict access to operator clients and monitor for suspicious activity related to client metadata manipulation during WebSocket connections.
Description
OpenClaw versions before 2026.3.28 have an authorization bypass vulnerability in the chat.send gateway method. The flaw arises because ACP-only provenance fields are controlled by client metadata from the WebSocket handshake, which is self-declared and not verified against the actual authorization state. This allows authenticated operator clients to spoof ACP identity labels and inject reserved provenance fields intended only for the ACP bridge by manipulating client metadata during connection.