CVE-2026-32034
Authentication Bypass in OpenClaw Control UI via Insecure HTTP
Publication date: 2026-03-19
Last updated on: 2026-03-25
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.21 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions prior to 2026.2.21 and involves an authentication bypass in the Control UI. It occurs when the allowInsecureAuth setting is explicitly enabled and the gateway is exposed over unencrypted HTTP connections. Under these conditions, attackers can bypass device identity and pairing verification.
An attacker who has leaked or intercepted credentials can exploit this flaw to gain high-privilege access to the Control UI because secure authentication enforcement is not applied over plaintext HTTP.
How can this vulnerability impact me? :
The vulnerability can allow attackers to bypass authentication controls and gain high-privilege access to the Control UI of the affected OpenClaw device.
This unauthorized access could lead to control over device functions, potentially compromising the security and operation of the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know