Unauthorized node-event injection via device-less role claim
Published Mar 19, 2026 · Updated Mar 19, 2026
Incorrect authorization in OpenClaw before 2026.2.22 allows remote authenticated users to inject node events through the Gateway. The WebSocket connect handler treated successful shared-token authentication as sufficient to skip device identity for every role, so a client could claim role=node and invoke node.event without pairing. Possession of the shared gateway token is required; exploitation can trigger agent requests and voice-transcript flows but does not interrupt the Gateway.
Summary
What happened
Incorrect authorization in OpenClaw before 2026.2.22 allows remote authenticated users to inject node events through the Gateway. The WebSocket connect handler treated successful shared-token authentication as sufficient to skip device identity for every role, so a client could claim role=node and invoke node.event without pairing. Possession of the shared gateway token is required; exploitation can trigger agent requests and voice-transcript flows but does not interrupt the Gateway.
The record
- CVE
- CVE-2026-32001
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 19, 2026CVE publishedPublication date reported by the CVE source.
- Mar 19, 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.2.22
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.
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