GHSA-r6xh-pqhr-v4xh — HIGH AI Security Vulnerability

Q: What is GHSA-r6xh-pqhr-v4xh?

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

Q: Is GHSA-r6xh-pqhr-v4xh actively exploited?

No confirmed active exploitation of GHSA-r6xh-pqhr-v4xh has been reported, but organizations should still patch proactively.

Q: How to fix GHSA-r6xh-pqhr-v4xh?

Update to patched version: openclaw 2026.4.22.

Q: What is the CVSS score for GHSA-r6xh-pqhr-v4xh?

No CVSS score has been assigned yet.

## 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,...

Full CISO analysis pending enrichment.

Affected Systems

Package	Ecosystem	Vulnerable Range	Patched
openclaw	npm	<= 2026.4.21	`2026.4.22`
4 dependents 93% patched ~0d to patch Full package profile →

Do you use openclaw? You're affected.

Severity & Risk

CVSS 3.1

N/A

EPSS

N/A

Exploitation Status

No known exploitation

Sophistication

N/A

Recommended Action

Patch available

Update openclaw to version 2026.4.22

Compliance Impact

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is GHSA-r6xh-pqhr-v4xh?

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

Is GHSA-r6xh-pqhr-v4xh actively exploited?

No confirmed active exploitation of GHSA-r6xh-pqhr-v4xh has been reported, but organizations should still patch proactively.

How to fix GHSA-r6xh-pqhr-v4xh?

Update to patched version: openclaw 2026.4.22.

What is the CVSS score for GHSA-r6xh-pqhr-v4xh?

No CVSS score has been assigned yet.

Technical Details

NVD Description

## 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.