Openclaw cli: OpenClaw: fetch-guard forwards custom authorization headers across cross-origin redirects (CVE-2026-32913)

OpenClaw's fetchWithSsrFGuard(...) function followed cross-origin redirects while preserving arbitrary caller-supplied headers except for a narrow denylist that excluded only Authorization, Proxy-Authorization, Cookie, and Cookie2 headers. This allowed other sensitive custom authorization headers such as X-Api-Key and Private-Token to be forwarded to different origins after a redirect. The vulnerability was addressed by switching from a denylist approach to an allowlist approach, permitting only safe headers like content negotiation and cache validators to be forwarded across origins. The affected npm package versions are >=2026.1.29 and <2026.3.7, with the fix released in 2026.3.7.

A remote service that can trigger a cross-origin redirect could receive sensitive custom authorization headers intended only for the original destination. This exposure risks leaking API keys, bearer tokens, or private tokens to unintended third-party origins, potentially leading to unauthorized access or data compromise. The CVSS score is 9.3 (critical), reflecting network attack vector, low attack complexity, no privileges or user interaction required, scope change, high confidentiality impact, and low integrity impact.

A patch is available and should be applied. Users should upgrade openclaw to version 2026.3.7 or later, which implements a safe-header allowlist for cross-origin redirects, preventing sensitive custom authorization headers from being forwarded. No additional mitigation is required beyond applying the official fix.