Privileged Control UI access via token-only authentication
Published Mar 19, 2026 · Updated Mar 19, 2026
Authentication bypass in OpenClaw before 2026.2.21 allows remote authenticated users to gain privileged Control UI access over HTTP. The WebSocket connection handler treated allowInsecureAuth as permission to accept token-only authentication and skip secure-context, device-identity, and pairing checks. Exploitation requires an affected gateway with that setting enabled, plaintext HTTP exposure, and a leaked or intercepted token or password; successful access grants privileged operator control.
Summary
What happened
Authentication bypass in OpenClaw before 2026.2.21 allows remote authenticated users to gain privileged Control UI access over HTTP. The WebSocket connection handler treated allowInsecureAuth as permission to accept token-only authentication and skip secure-context, device-identity, and pairing checks. Exploitation requires an affected gateway with that setting enabled, plaintext HTTP exposure, and a leaked or intercepted token or password; successful access grants privileged operator control.
The record
- CVE
- CVE-2026-32034
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-285, CWE-319, 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.21
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