https://db.gcve.eu/rss/recent/all/10 Most recent entries from all 2026-10-01T19:46:13.293407+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent entries. https://db.gcve.eu/vuln/cve-2026-44118 CVE-2026-44118 — OpenClaw < 2026.4.22 - Owner Context Spoofing via Bearer Token Header 2026-10-01T19:46:13.295983+00:00

Affected: OpenClaw

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.

 https://db.gcve.eu/vuln/ghsa-r6xh-pqhr-v4xh GHSA-r6xh-pqhr-v4xh — OpenClaw: MCP loopback owner context is derived from server-issued bearer tokens 2026-10-01T19:46:13.296089+00:00

Affected: npm: openclaw

## 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. - openclaw@2026.4.22 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.