Advisory

GHSA-pfv7-rr5m-qmv6

Also known as: None

Summary

OpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint

Details

Summary

When the optional Chrome extension relay is enabled, /extension accepted unauthenticated WebSocket upgrades while /json/* and /cdp required auth.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Affected: <= 2026.2.17
  • Latest published npm version at triage time: 2026.2.17

Impact

This is a local-only issue on loopback (127.0.0.1) and only applies when the extension relay feature is in use. A local process on the same machine could connect to /extension without the token and interfere with extension-relay behavior.

No remote network exploit path is involved.

Fix

  • Require gateway-token auth on both /extension and /cdp relay WebSocket endpoints.
  • Keep loopback/origin checks as defense-in-depth, not as authentication.
  • Use one token path in setup: gateway.auth.token / OPENCLAW_GATEWAY_TOKEN.

Fix Commit(s)

  • 7e54b6c96feb1a5c30884f2b32037b8dadd0e532

OpenClaw thanks @tdjackey for reporting.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-03-03 21:42 UTC
Modified
2026-03-04 15:16 UTC

Affected packages and fixes

openclaw

npm · All systems

Affected

  • introduced 0, fixed 2026.2.19 (semver)

Fixed versions

2026.2.19

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences