Unauthenticated plugin API access via path mismatch
Published Mar 19, 2026 · Updated Mar 19, 2026
Authentication bypass in OpenClaw before 2026.2.26 allows remote attackers to access protected plugin channel APIs over HTTP. The server-http guard checks only exact raw /api/channels paths, while plugin handlers can decode or lowercase alternate encodings before routing them. A reachable Gateway with a canonicalizing plugin route is required, and the bypass permits unauthorized access and actions exposed by that plugin API.
Summary
What happened
Authentication bypass in OpenClaw before 2026.2.26 allows remote attackers to access protected plugin channel APIs over HTTP. The server-http guard checks only exact raw /api/channels paths, while plugin handlers can decode or lowercase alternate encodings before routing them. A reachable Gateway with a canonicalizing plugin route is required, and the bypass permits unauthorized access and actions exposed by that plugin API.
The record
- CVE
- CVE-2026-32031
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-288, T1190
- Attack vector
- network
- Privileges
- unauthenticated
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.26
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
- Alternate-path request examplesproof of concept · demonstrated
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