# CVE-2026-44118: openclaw — Fixed in 2026.4.22

📦 npm

Not in CISA KEV

# CVE-2026-44118 — openclaw

[Fix: openclaw/openclaw@3cb1a56](https://github.com/openclaw/openclaw/commit/3cb1a56bfc9579a0f2336f9cfa12a8a744332a19)

CVE-2026-44118 is a CWE-290 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw < 2026.4.22 - Owner Context Spoofing via Bearer Token Header

Also known as[GHSA-r6xh-pqhr-v4xh](/vulnerability/GHSA-r6xh-pqhr-v4xh)

Published

May 6, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   A successful exploit gives an attacker total control of the affected component, not partial access.
-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-44118.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs3th percentile — riskier than 3% of all scored CVEsHighest risk

0.00%0.22%0.44%0.66%0.0%0.1%Jun 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

132other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`openclaw`npm

2.4Mdownloads / week

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

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

📦npm

`openclaw` 

all versions

2026.4.22`npm install openclaw@2026.4.22`

## Affected Products

1 product · 1 configurations

Application

`openclaw`openclaw

< 2026.4.22

range

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update openclaw to 2026.4.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44118 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
    

## Frequently Asked Questions

\## 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 hea

O3 Security · Impact-Aware SCA

### Is CVE-2026-44118 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)