Owner-gated MCP access via spoofed header
Published May 6, 2026 · Updated May 6, 2026
Authentication bypass in OpenClaw before 2026.4.22 allows local users to access owner-gated MCP operations with a non-owner token. The loopback MCP request handler trusted the caller-controlled x-openclaw-sender-is-owner header instead of deriving owner status from the authenticated bearer class. Exploitation requires a non-owner loopback bearer and permits the local client to invoke tools reserved for the owner.
Summary
What happened
Authentication bypass in OpenClaw before 2026.4.22 allows local users to access owner-gated MCP operations with a non-owner token. The loopback MCP request handler trusted the caller-controlled x-openclaw-sender-is-owner header instead of deriving owner status from the authenticated bearer class. Exploitation requires a non-owner loopback bearer and permits the local client to invoke tools reserved for the owner.
The record
- CVE
- CVE-2026-44118
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-290
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 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.4.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.
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