Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

OpenClaw < 2026.4.22 - Owner Context Spoofing via Bearer Token Header

CVSS 4.0 8.5 HIGHCVSS 3.1 7.8 HIGHEUVD CVSS 4.0 8.5 CVSS 4.0 · [email protected] · Secondary 8.5 HIGHCVSS 3.1 · [email protected] · Secondary 7.8 HIGHCVSS_V3 CVSS_V4 Publisher rating HIGHFixed by openclaw 2026.4.22KEV status unknown

cve-program · CVE-2026-44118

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-28201

Published

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.

Read the publisher's advisory

nvd · CVE-2026-44118

Published

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.

Read the publisher's advisory

osv · GHSA-r6xh-pqhr-v4xh

Published

## Summary MCP loopback owner context is derived from server-issued bearer tokens. ## Affected Packages / Versions - Package: openclaw (npm) - Affected versions: <= 2026.4.21 - Fixed version: 2026.4.22 ## Impact The loopback MCP path accepted spoofable owner-context metadata from request headers, which could allow a non-owner loopback client to present itself as owner for owner-gated operations. ## Fix The MCP loopback runtime now issues separate owner and non-owner bearer tokens and derives senderIsOwner exclusively from which token authenticated the request. The spoofable sender-owner header is no longer emitted or trusted. ## Fix Commit(s) - 3cb1a56bfc9579a0f2336f9cfa12a8a744332a19 ## Verification - The fix commit is contained in the public v2026.4.22 tag. - [email protected] is published on npm and the compiled package contains the fix. - Focused regression coverage for this path passed before publication. OpenClaw thanks @VladimirEliTokarev for reporting.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-44118

Published

OpenClaw

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "OpenClaw",
                    "product": "OpenClaw",
                    "defaultStatus": "unaffected",
                    "packageURL": "pkg:npm/openclaw",
                    "versions": [
                        {
                            "version": "0",
                            "status": "affected",
                            "versionType": "semver",
                            "lessThan": "2026.4.22"
                        },
                        {
                            "version": "2026.4.22",
                            "status": "unaffected",
                            "versionType": "semver"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-28201

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: May 6, 2026, 7:49:37 PM

dateUpdated: Sep 24, 2026, 2:17:45 PM

1 related source bulletins · separate from aliases

WID-SEC-W-2026-1253: OpenClaw: Mehrere Schwachstellen

CVE-2026-44113 · CVE-2026-44114 · CVE-2026-44115 · CVE-2026-44116 · CVE-2026-44118 · CVE-2026-44994 · CVE-2026-45003

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-44118

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-290

Original publisher date fields

published: 2026-05-06T20:16:35.900

lastModified: 2026-06-17T10:50:17.423

1 source CPE criteria · context only
  • cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-r6xh-pqhr-v4xh

Published

openclaw

npm

SEMVER · introduced 0 → fixed 2026.4.22

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 12 Nov 14:22 UTC · 274 of 275 readable · 272 fully read · documentation 469/469 current