Advisory

GHSA-r6xh-pqhr-v4xh

Also known as: CVE-2026-44118

Summary

OpenClaw: MCP loopback owner context is derived from server-issued bearer tokens

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-05-04 20:22 UTC
Modified
2026-05-12 17:26 UTC

Affected packages and fixes

openclaw

npm · All systems

Affected

  • introduced 0, fixed 2026.4.22 (semver)

Fixed versions

2026.4.22

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences