What is the CVSS score of CVE-2026-32913?

CVE-2026-32913 has a CVSS 3.1 base score of 9.3 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N. EPSS exploitation probability: 0.0%.

Which versions of Openclaw are affected by CVE-2026-32913?

A critical vulnerability in OpenClaw versions prior to 2026.3.7 allows attackers to steal sensitive API credentials and authentication tokens through malicious redirects, potentially compromising…. A patch is available.

How to fix or mitigate CVE-2026-32913?

Within 24 hours: Identify all systems running OpenClaw versions prior to 2026.3.7 and assess business criticality. Within 7 days: Apply vendor patch to version 2026.3.7 or later across all instances; prioritize production environments first. Within 30 days: Audit API key and token usage logs for unauthorized access patterns, rotate all exposed credentials (X-Api-Key, Private-Token headers), and validate redirect destinations in application configuration.

Openclaw CVE-2026-32913

EUVD-2026-14599 CRITICAL

Insufficiently Protected Credentials (CWE-522)

2026-03-23 VulnCheck

GHSA-6mgf-v5j7-45cr

Information Disclosure Openclaw

9.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.3 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

Low

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Mar 23, 2026 - 22:00 euvd

EUVD-2026-14599

Analysis Generated

Mar 23, 2026 - 22:00 vuln.today

Patch released

Mar 23, 2026 - 22:00 nvd

Patch available

CVE Published

Mar 23, 2026 - 21:36 nvd

CRITICAL 9.3

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

2 npm packages depend on openclaw (2 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.3.7.

DescriptionCVE.org

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.

AnalysisAI

OpenClaw versions prior to 2026.3.7 contain a critical header validation flaw in the fetchWithSsrFGuard function that leaks sensitive authorization headers (including X-Api-Key and Private-Token) across cross-origin redirects. An attacker can exploit this remotely without authentication by triggering HTTP redirects to attacker-controlled domains, intercepting credentials intended for legitimate services. With a CVSS score of 9.3 and network-accessible attack vector requiring low complexity, this represents a significant information disclosure risk, though no active exploitation (KEV) or public POC has been reported at this time.

Technical ContextAI

This vulnerability affects OpenClaw (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*), specifically the fetchWithSsrFGuard function which performs server-side request guarding. The root cause is CWE-522 (Insufficiently Protected Credentials), where the application fails to properly validate and strip sensitive HTTP headers when following cross-origin redirects. When an HTTP 301/302 redirect occurs during fetch operations, custom authorization headers that should remain private to the original destination are incorrectly forwarded to the redirect target. This violates the principle of least privilege for credential transmission and the same-origin policy expectations for sensitive headers. The vulnerability enables a classic header-forwarding attack pattern where redirect chains can be weaponized to extract authentication tokens.

RemediationAI

Upgrade OpenClaw to version 2026.3.7 or later immediately, as a patch is available from the vendor (see https://github.com/openclaw/openclaw/security/advisories/GHSA-6mgf-v5j7-45cr). The specific fix is implemented in commit 46715371b0612a6f9114dffd1466941ac476cef5 available at https://github.com/openclaw/openclaw/commit/46715371b0612a6f9114dffd1466941ac476cef5. Until patching is possible, implement strict egress filtering to prevent the application from making outbound requests to untrusted domains, and consider using a secure proxy that strips sensitive headers on cross-origin redirects. Review application logs for any suspicious redirect patterns to external domains that may indicate exploitation attempts. If fetchWithSsrFGuard is used with third-party APIs, rotate all API keys and tokens that may have been exposed through redirect chains.