OpenClaw before 2026.4.22 derives loopback MCP owner context from spoofable server-issued bearer tokens in request headers. Non-owner loopback clients can present themselves as owner to bypass owner-gated operations by manipulating the sender-owner header metadata.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Wed, 06 May 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenClaw before 2026.4.22 derives loopback MCP owner context from spoofable server-issued bearer tokens in request headers. Non-owner loopback clients can present themselves as owner to bypass owner-gated operations by manipulating the sender-owner header metadata. | |
| Title | OpenClaw < 2026.4.22 - Owner Context Spoofing via Bearer Token Header | |
| First Time appeared |
Openclaw
Openclaw openclaw |
|
| Weaknesses | CWE-290 | |
| CPEs | cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Openclaw
Openclaw openclaw |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-05-06T19:49:37.173Z
Reserved: 2026-05-05T11:30:46.260Z
Link: CVE-2026-44118
No data.
Status : Awaiting Analysis
Published: 2026-05-06T20:16:35.900
Modified: 2026-05-06T21:20:52.707
Link: CVE-2026-44118
No data.
OpenCVE Enrichment
Updated: 2026-05-07T00:15:05Z
Weaknesses