CVE-2026-22174: OpenClaw Loopback CDP probe can leak Gateway token to local listener
Summary A local process can capture the OpenClaw Gateway auth token from Chrome CDP probe traffic on loopback. Details Affected versions inject x-openclaw-relay-token for loopback CDP URLs, and CDP reachability probes send that header to /json/version. If an attacker controls the probed loopback port, they can read that token and reuse it as Gateway bearer auth.
Published Mar 3, 2026 · Updated Mar 18, 2026
Affected packages
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.2.21-2
- Fixed in
- 2026.2.22
- Check
npm ls openclaw
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A local process can capture the OpenClaw Gateway auth token from Chrome CDP probe traffic on loopback.
Details
Affected versions inject x-openclaw-relay-token for loopback CDP URLs, and CDP reachability probes send that header to /json/version. If an attacker controls the probed loopback port, they can read that token and reuse it as Gateway bearer auth.
Relevant code paths (pre-fix):
src/browser/extension-relay.ts(getChromeExtensionRelayAuthHeaders)src/browser/cdp.helpers.ts(getHeadersWithAuth)src/browser/chrome.ts(fetchChromeVersion)
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published (at triage):
2026.2.21-2 - Vulnerable:
<= 2026.2.21-2 - Patched: >= 2026.2.22
Deployment Model Applicability
This does not change OpenClaw’s documented security model for standard single-owner installs (you own the machine/VPS and trust local processes under that OS account boundary). Risk is for non-standard shared-user/shared-host installs where an untrusted local user/process can race/bind the loopback relay port.
Impact
- Local credential disclosure.
- Follow-on impact depends on local deployment and enabled Gateway capabilities.
Fix Commit(s)
afa22acc4a09fdf32be8a167ae216bee85c30dad
Release Process Note
Patched version is set to >= 2026.2.22 for the published release.
OpenClaw thanks @tdjackey for reporting.
Credited to tdjackey.
References
- https://github.com/openclaw/openclaw/security/advisories/GHSA-v3j7-34xh-6g3w
- https://github.com/openclaw/openclaw/commit/afa22acc4a09fdf32be8a167ae216bee85c30dad
- https://nvd.nist.gov/vuln/detail/CVE-2026-22174
- https://www.vulncheck.com/advisories/openclaw-gateway-token-disclosure-via-chrome-cdp-probe
- https://github.com/advisories/GHSA-v3j7-34xh-6g3w
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026CVE-2026-53812
OpenClaw's browser act interactions could bypass private-network navigation checks
medium7.7Jul 2, 2026
