A local process can capture the OpenClaw Gateway auth token from Chrome CDP probe traffic on loopback.
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)
openclaw (npm)2026.2.21-2<= 2026.2.21-2This 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.
afa22acc4a09fdf32be8a167ae216bee85c30dadPatched version is set to >= 2026.2.22 for the published release.
OpenClaw thanks @tdjackey for reporting.
{
"github_reviewed": true,
"github_reviewed_at": "2026-03-03T21:50:34Z",
"cwe_ids": [
"CWE-290",
"CWE-306"
],
"severity": "MODERATE",
"nvd_published_at": "2026-03-18T02:16:21Z"
}