Authenticated provenance injection via spoofed client metadata
Published Apr 20, 2026 · Updated Apr 20, 2026
Authorization bypass in OpenClaw before 2026.3.28 allows remote authenticated users to inject reserved ACP provenance via chat.send. The chat.send handler trusted ACP identity labels supplied in WebSocket handshake metadata instead of checking the caller's verified operator.admin scope. An authenticated operator.write client can therefore forge source labels and provenance receipts that alter agent-visible message context; no code execution or service interruption is reported.
Summary
What happened
Authorization bypass in OpenClaw before 2026.3.28 allows remote authenticated users to inject reserved ACP provenance via chat.send. The chat.send handler trusted ACP identity labels supplied in WebSocket handshake metadata instead of checking the caller's verified operator.admin scope. An authenticated operator.write client can therefore forge source labels and provenance receipts that alter agent-visible message context; no code execution or service interruption is reported.
The record
- CVE
- CVE-2026-41299
- Published
- Apr 20, 2026
- Updated
- Apr 20, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-807, CWE-290, T1036
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 20, 2026CVE publishedPublication date reported by the CVE source.
- Apr 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.3.28
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo