Is this vulnerability remotely exploitable?

Yes. If an attacker can control or influence redirect targets, or operate an endpoint that OpenClaw contacts with sensitive headers, they can remotely trigger cross-origin redirects that expose those headers.

What level of access does an attacker need to exploit this issue?

An attacker typically needs the ability to control the destination of a redirect in a workflow that uses fetchWithSsrFGuard, or to host a service that OpenClaw will call with credentials attached. They do not need direct access to the OpenClaw server itself.

What is the safest general fix pattern for this vulnerability?

The safest pattern is to never forward sensitive headers across origin boundaries: strip authorization-like headers on cross-origin redirects, and only attach them to requests whose final destination is a known, trusted origin.

Severity:

CRITICAL RISK

(9.3)

Improper Sensitive Header Handling (CWE-522) in OpenClaw fetchWithSsrFGuard Cross-Origin Redirects

CVE-2026-32913

Published:

Mar 23, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Improper Protection of Credentials

CWE:

CWE-522

Impact:

Exposure of Authentication Tokens and API Keys via Cross-Origin Redirects

Severity:

CRITICAL RISK

(9.3)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Protection of Credentials

CWE:

CWE-522

Impact:

Exposure of Authentication Tokens and API Keys via Cross-Origin Redirects

Severity:

CRITICAL RISK

(9.3)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Improper Sensitive Header Handling (CWE-522) in OpenClaw fetchWithSsrFGuard Cross-Origin Redirects

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal