Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Owner context spoofing privilege escalation in OpenClaw loopback MCP

IdentifiersCVE-2026-44118CWE-290· Authentication Bypass by Spoofing

CVE-2026-44118 is an improper access control / identity spoofing flaw in OpenClaw affecting versions before 2026.4.22. In the loopback MCP runtime, OpenClaw derived owner context from spoofable, server-issued bearer-token-associated request header metadata rather than binding owner status to the authenticated session. Specifically, OpenClaw trusted a client-controlled ownership indicator (described in reporting as senderIsOwner / sender-owner header metadata) without cross-referencing it against the bearer token that authenticated the request. As a result, a non-owner loopback client with a valid authentication token could manipulate the ownership metadata and be treated as the owner, bypassing owner-gated operations.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a locally running non-owner process to escalate privileges to owner-level control within OpenClaw. Reported impacts include unauthorized access to and control over gateway configuration, cron/scheduling, and execution environment management. In the broader Claw Chain, this privilege escalation can be used as a pivot to administrator-equivalent control of the agent runtime, enabling follow-on abuse of the agent's privileges for data access, operational manipulation, and persistence.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict local access to the OpenClaw loopback/MCP interface to only trusted processes and users, minimize which local processes can obtain valid bearer tokens, and reduce exposure of owner-capable runtime functions such as gateway configuration, scheduling, and execution management. Monitor for anomalous owner-only operations originating from loopback clients, and rotate potentially exposed tokens/secrets after patching. Restrict exposed instances behind authentication and firewall controls where applicable.

Remediation

Patch, then assume compromise.

Upgrade OpenClaw to version 2026.4.22 or later. According to the provided content, OpenClaw fixed the issue by issuing separate owner and non-owner bearer tokens, deriving senderIsOwner exclusively from the token that authenticated the request, and no longer emitting or trusting the spoofable sender-owner header. Apply the April 23, 2026 fixes associated with GHSA-r6xh-pqhr-v4xh and related Claw Chain advisories as applicable.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenclawOpenclawapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.