CVE-2026-41299
Openclaw ≤ 2026.3.28
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/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:XSummary
CVE-2026-41299 is a high-severity Reliance on Untrusted Inputs in a Security Decision (CWE-807) vulnerability in Openclaw Openclaw. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-41299 is an authorization bypass vulnerability (CWE-807) affecting OpenClaw versions before 2026.3.28. The issue resides in the chat.send gateway method, where ACP-only provenance fields are protected solely by self-declared client metadata from the WebSocket handshake, rather than the verified authorization state. This allows manipulation during connection establishment, with a CVSS v3.1 base score of 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N), indicating network accessibility, low attack complexity, low privileges required, and primarily high integrity impact.
Authenticated operator clients can exploit this vulnerability by spoofing ACP identity labels and injecting reserved provenance fields meant exclusively for the ACP bridge. Attackers with operator-level access manipulate client metadata in the WebSocket handshake to bypass gates, enabling unauthorized injection of privileged data into chat.send operations.
Advisories recommend upgrading to OpenClaw 2026.3.28 or later to mitigate the issue, as detailed in the GitHub Security Advisory (GHSA-6xg4-82hv-cp6f) and VulnCheck advisory on client identity spoofing in chat.send gateway provenance guards.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-24006
Vulnerability Data
OpenClaw before 2026.3.28 contains an authorization bypass vulnerability in the chat.send gateway method where ACP-only provenance fields are gated by self-declared client metadata from WebSocket handshake rather than verified authorization state. Authenticated operator clients can spoof ACP identity labels and…
more
inject reserved provenance fields intended only for the ACP bridge by manipulating client metadata during connection.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Explicitly requires that every access decision be based on authoritative, protected decision data rather than caller-supplied inputs.
Input validation can reject malformed or attacker-controlled values before they reach a security decision point.
Access enforcement requires decisions to be made from trusted policy data rather than modifiable client-supplied inputs.
Information-flow enforcement applies rules to validated, internal attributes instead of untrusted external values.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Strong authentication mechanisms directly prevent security decisions from depending on modifiable, untrusted inputs.
Verification and protection of identity assertions stops reliance on attacker-controlled values for authorization decisions.
Proper management of identities/credentials reduces the chance that security decisions will be driven by untrusted inputs.
Policy-driven, least-privilege authorization reduces opportunities to bypass controls via tampered inputs.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards directly prohibit using untrusted inputs for security-critical decisions.
Security testing in development catches input-validation flaws before deployment.
Monitoring can detect exploitation but does not stop the underlying weakness.
Application security requirements explicitly call for validation of inputs used in security decisions.
Secure architecture principles mandate treating all external inputs as untrusted.
Access-control rules can be bypassed if they rely on untrusted inputs.