Summary
OpenClaw: Gateway chat.send ACP-only provenance guard could be bypassed by client identity spoofing
ACP-only provenance fields in chat.send were gated by self-declared client metadata from the WebSocket handshake rather than verified authorization state.
Affected Component
src/gateway/server-methods/chat.ts, src/gateway/server/ws-connection/message-handler.ts
Fixed Versions
- Affected:
<= 2026.3.24 - Patched:
>= 2026.3.28 - Latest stable
2026.3.28contains the fix.
Impact
A normal authenticated operator client could spoof ACP identity labels and inject reserved provenance fields intended only for the ACP bridge.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Fixed by commit 4b9542716c (Gateway: require verified scope for chat provenance).
Frequently Asked Questions
- What is CVE-2026-41299? CVE-2026-41299 is a high-severity security vulnerability in openclaw (npm), affecting versions <= 2026.3.24. It is fixed in 2026.3.28.
- Which versions of openclaw are affected by CVE-2026-41299? openclaw (npm) versions <= 2026.3.24 is affected.
- Is there a fix for CVE-2026-41299? Yes. CVE-2026-41299 is fixed in 2026.3.28. Upgrade to this version or later.
- Is CVE-2026-41299 exploitable, and should I be worried? Whether CVE-2026-41299 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-41299 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-41299? Upgrade
openclawto 2026.3.28 or later.