Skip to main content
VulnerabilityPublished Updated

CVE-2026-32913: OpenClaw · fetch-guard forwards custom authorization headers across cross-origin redirects

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 2026.3.7 as a priority.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.7.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.3.7
Fixed in
  • 2026.3.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

Description

OpenClaw CLI versions up to 2026.3.2 have a vulnerability in the fetchWithSsrFGuard function where custom authorization headers are forwarded across cross-origin redirects. This can expose sensitive headers like X-Api-Key or Private-Token to unintended origins. The issue is fixed in version 2026.3.7 by replacing a narrow denylist with a safe allowlist for headers forwarded during redirects.

References

Community reviews

Loading reviews…