Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

OpenClaw's Browser Relay /cdp websocket is missing auth which could allow cross-tab cookie access

CVE-2026-28458GHSA-mr32-vwc2-5j6h

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm openclaw

    Affected
    >= 2026.1.20, < 2026.2.1
    Fixed in
    2026.2.1

  • npm moltbot

    Affected
    <= 0.1.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-28458: 0.35% estimated exploitation activity in the next 30 days; percentile 28.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-mr32-vwc2-5j6h

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-mr32-vwc2-5j6h

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-28458

Advisory: OpenClaw's Browser Relay /cdp websocket is missing auth which could allow cross-tab cookie access
IDs: CVE-2026-28458, GHSA-mr32-vwc2-5j6h
Record: https://patchnext.com/advisories/cve-2026-28458 (revision 3, source checked 26 Oct 2026, 12:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: openclaw 2026.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm openclaw: affected >= 2026.1.20, < 2026.2.1; fixed in 2026.2.1
- npm moltbot: affected <= 0.1.0

## Suggested inspection (read-only)
- `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls moltbot --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openclaw, moltbot.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-mr32-vwc2-5j6h (OSV record GHSA-mr32-vwc2-5j6h lists affected ranges: npm openclaw >=2026.1.20 =0 <=0.1.0)
- Verified: https://github.com/advisories/GHSA-mr32-vwc2-5j6h (GitHub-reviewed advisory GHSA-mr32-vwc2-5j6h lists affected ranges: npm openclaw >=2026.1.20 =0 <=0.1.0)

Commands are suggestions: review each one before running it.

Loading voting…