How severe is CVE-2026-28458?

No CVSS score has been assigned to CVE-2026-28458 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-28458?

CVE-2026-28458 affects the following packages: openclaw (npm), moltbot (npm). Ecosystems affected: npm.

How do I fix CVE-2026-28458?

Update openclaw to 2026.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28458 is resolved across your whole dependency graph.

How do I detect CVE-2026-28458 in my npm dependencies?

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.

How do I mitigate CVE-2026-28458 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2026-28458?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-28458 can be triaged on real exposure rather than presence alone.

Is CVE-2026-28458 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-28458 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-28458?

CVE-2026-28458 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 22th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-28458?

CVE-2026-28458 is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-28458 published, and has it been updated?

CVE-2026-28458 was published on March 5, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-28458 — openclaw

Fix: openclaw/openclaw@a1e89af

CVE-2026-28458 is a Missing Authentication vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw 2026.1.20 < 2026.2.1 - Missing Authentication in Browser Relay /cdp WebSocket Endpoint

Also known asGHSA-mr32-vwc2-5j6h

Published

Mar 5, 2026

Updated

Aug 12, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Sep 21, 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-28458.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs22th percentile — riskier than 22% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs 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.

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

openclawnpm

2.5Mdownloads / week

moltbotnpm

284downloads / week

Description

Summary

In affected versions, the Browser Relay /cdp WebSocket endpoint did not require an authentication token. As a result, a website running in the browser could potentially connect to the local relay (via loopback WebSocket) and use CDP to access cookies from other open tabs and run JavaScript in the context of other tabs.

Affected Packages / Versions

npm: openclaw >= 2026.1.20, < 2026.2.1
npm: moltbot <= 0.1.0

Details

The Chrome extension Browser Relay service exposes a local WebSocket endpoint at ws://127.0.0.1:18792/cdp (default port) for forwarding Chrome DevTools Protocol (CDP) messages.

In affected versions, the /cdp upgrade path verified the TCP peer was loopback but did not require a shared secret and did not block browser-initiated cross-origin requests.

Impact

Potential disclosure of sensitive information (for example, session cookies from other open tabs)
Potential JavaScript execution in the context of other open tabs

Users must have the Browser Relay extension installed and active, and must visit an untrusted site.

Fix

openclaw now requires a per-instance shared secret header for Browser Relay access:

HTTP header: x-openclaw-relay-token

It also rejects /cdp WebSocket upgrades when the Origin header is present but is not chrome-extension://..., and refuses /cdp connections unless the extension is connected.

Fix Commit(s)

a1e89afcc19efd641c02b24d66d689f181ae2b5c

Releases

[email protected] includes the fix.
Latest published openclaw at time of writing: 2026.2.13.

Mitigation

Update to openclaw@>= 2026.2.1.
If you cannot update immediately, disable the Browser Relay extension / relay server and avoid visiting untrusted sites.

Thanks @johnatzeropath, @LeftenantZero, and @yueyueL for reporting.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.1.20&&< 2026.2.1	2026.2.1`npm install openclaw@2026.2.1`
📦npm	`moltbot`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update openclaw to 2026.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28458 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-28458 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-28458. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary In affected versions, the Browser Relay `/cdp` WebSocket endpoint did not require an authentication token. As a result, a website running in the browser could potentially connect to the local relay (via loopback WebSocket) and use CDP to access cookies from other open tabs and run JavaScript in the context of other tabs. ### Affected Packages / Versions - npm: `openclaw` `>= 2026.1.20, < 2026.2.1` - npm: `moltbot` `<= 0.1.0` ### Details The Chrome extension Browser Relay service exposes a local WebSocket endpoint at `ws://127.0.0.1:18792/cdp` (default port) for forwarding Chrome

O3 Security · Impact-Aware SCA

Is CVE-2026-28458 in your dependencies?

O3 Security finds CVE-2026-28458 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works