Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-32913 – Sensitive API Token Leakage via Cross-Origin Redirect – OpenClaw < 2026.3.7

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-32913 is a critical-severity improper header validation vulnerability in OpenClaw, an npm package, affecting all versions prior to 2026.3.7. The flaw resides in the fetchWithSsrFGuard function, which incorrectly forwards custom authorization headers — including X-Api-Key and Private-Token — to attacker-controlled origins when a cross-origin HTTP redirect is followed. With a CVSS v3.1 base score of 9.1 (Critical), this vulnerability is remotely exploitable without authentication or user interaction, and poses a direct risk of API credential theft.

Technical details

  • Root cause: fetchWithSsrFGuard used a narrow denylist to strip headers on cross-origin redirects, blocking only Authorization, Proxy-Authorization, Cookie, and Cookie2. Custom authorization headers such as X-Api-Key and Private-Token were not included in this denylist and were therefore forwarded across origin boundaries.
  • Trigger conditions: An attacker must control or compromise a service capable of issuing an HTTP redirect to a different origin — the redirect causes OpenClaw to forward the caller’s sensitive custom headers to the attacker’s destination.
  • Attack vector: Network — remotely exploitable with no privileges required and no user interaction needed.
  • Impact: An attacker receiving redirected requests captures custom authorization credentials (API keys, private tokens, bearer-style headers) that were intended exclusively for the original destination, enabling unauthorized access to protected APIs and backend services.
  • Fix: The patched version (2026.3.7) replaces the denylist approach with a safe-header allowlist (CROSS_ORIGIN_REDIRECT_SAFE_HEADERS), permitting only benign headers (e.g., content negotiation, cache validators) to survive cross-origin transitions. All custom authorization headers are stripped by default.
  • Public PoC: A public proof-of-concept repository has been published and is being tracked.

Affected software

  • OpenClaw (npm package) — all versions < 2026.3.7

Severity

  • CVSS v3.1 Base Score: 9.1 — CRITICAL
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • CWE-522: Insufficiently Protected Credentials

Mitigation and recommended actions

  • Immediate: Upgrade OpenClaw to version 2026.3.7 or later, which contains the vendor-supplied fix.
  • No supported workaround exists for unpatched versions. Organizations that cannot immediately upgrade should consider restricting network access to services running the vulnerable OpenClaw component and auditing logs for unexpected outbound redirect activity.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge