Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-r6xh-pqhr-v4xh | OpenClaw: MCP loopback owner context is derived from server-issued bearer tokens |
Thu, 07 May 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
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
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-05-07T17:22:50.507Z
Reserved: 2026-05-05T11:30:46.260Z
Link: CVE-2026-44118
Updated: 2026-05-07T17:22:28.236Z
Status : Analyzed
Published: 2026-05-06T20:16:35.900
Modified: 2026-05-07T17:07:19.353
Link: CVE-2026-44118
No data.
OpenCVE Enrichment
Updated: 2026-05-07T00:15:05Z
Github GHSA