MCP loopback owner context is derived from server-issued bearer tokens.
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.
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.
OpenClaw thanks @VladimirEliTokarev for reporting.
{
"github_reviewed_at": "2026-05-04T20:22:42Z",
"severity": "HIGH",
"cwe_ids": [
"CWE-284",
"CWE-290"
],
"github_reviewed": true,
"nvd_published_at": null
}