# CVE-2026-32913: OpenClaw < 2026.3.7 - Custom Authorization Header Leakage via Cross-Origin Redirects

> Attackers can intercept sensitive API keys and tokens by triggering cross-origin redirects in the OpenClaw library's fetch guard.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Mar 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-6mgf-v5j7-45cr, MINI-w7hw-39qg-r8vg

## What is CVE-2026-32913?

CVE-2026-32913 is a high-severity vulnerability in Openclaw Openclaw, published on 23 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenClaw before 2026.3.7 contains an improper header validation vulnerability in fetchWithSsrFGuard that forwards custom authorization headers across cross-origin redirects. Attackers can trigger redirects to different origins to intercept sensitive headers like X-Api-Key and Private-Token intended for the original destination.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-32913?

2 open source packages ship an affected version, including openclaw. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | All versions | 2026.3.7 |
| `openclaw` | npm | All versions | 2026.3.7 |

Products: Openclaw Openclaw.

## How do I fix CVE-2026-32913?

Upgrade openclaw to 2026.3.7 or later.

## Is CVE-2026-32913 being exploited?

There is no known exploitation of CVE-2026-32913 in the wild and no public exploit code.

Public exploit code:

- I Found a Zero-Day Vulnerability in OpenClaw — Here’s How It Went (github_poc): https://github.com/Rickidevs/CVE-2026-32913

## Other vulnerabilities in Openclaw Openclaw

- [CVE-2026-28363](https://insights.sbomify.com/CVE-2026-28363/): Security feature bypass in OpenClaw (critical 9.9)
- [CVE-2026-30741](https://insights.sbomify.com/CVE-2026-30741/): Code injection in n/a (critical 9.8)
- [CVE-2026-33579](https://insights.sbomify.com/CVE-2026-33579/): OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval (critical 9.4)
- [CVE-2026-32922](https://insights.sbomify.com/CVE-2026-32922/): OpenClaw < 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate (critical 9.4)
- [CVE-2026-32978](https://insights.sbomify.com/CVE-2026-32978/): OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32913 and fix it if it is affected.

What it is: CVE-2026-32913 is a high-severity vulnerability in Openclaw Openclaw, published on 23 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32913 in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.3.7
- openclaw (npm): affected all versions; fixed in 2026.3.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32913/ (Markdown: https://insights.sbomify.com/CVE-2026-32913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32913
- OSV: https://osv.dev/vulnerability/CVE-2026-32913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32913/
Summaries are generated and may contain mistakes; the official description above is the record.