CVE-2026-33397

Angular SSR Vulnerable to Protocol-Relative URL Injection via Single Backslash Bypass

MEDIUM
6.1
CVSS Score
Published: March 26, 2026 at 01:46 PM UTC
Updated: June 17, 2026 at 10:37 AM UTC
1 product affected across 1 vendorAngular CLI

Using angular-cli by angular?

Get instant alerts when new vulnerabilities affect angular-cli - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.1
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

The Angular SSR is a server-rise rendering tool for Angular applications. Versions on the 22.x branch prior to 22.0.0-next.2, the 21.x branch prior to 21.2.3, and the 20.x branch prior to 20.3.21 have an Open Redirect vulnerability in `@angular/ssr` due to an incomplete fix for CVE-2026-27738. While the original fix successfully blocked multiple leading slashes (e.g., `///`), the internal validation logic fails to account for a single backslash (`\`) bypass. When an Angular SSR application is deployed behind a proxy that passes the `X-Forwarded-Prefix` header, an attacker provides a value starting with a single backslash, the internal validation failed to flag the single backslash as invalid, the application prepends a leading forward slash, resulting in a `Location` header containing the URL, and modern browsers interpret the `/\` sequence as `//`, treating it as a protocol-relative URL and redirecting the user to the attacker-controlled domain. Furthermore, the response lacks the `Vary: X-Forwarded-Prefix` header, allowing the malicious redirect to be stored in intermediate caches (Web Cache Poisoning). Versions 22.0.0-next.2, 21.2.3, and 20.3.21 contain a patch. Until the patch is applied, developers should sanitize the `X-Forwarded-Prefix` header in their `server.ts` before the Angular engine processes the request.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 20.3.21v < 21.2.3v < 22.0.0-next.220.0.0 ≤ v < 20.3.2121.0.0 ≤ v < 21.2.322.0.0 next022.0.0 next1
Affected range stops below 20.3.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.0.0-next.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/angular/angular-cli/pull/32771
x_refsource_MISCNot Applicable
Source: cverecord
https://github.com/advisories/GHSA-xh43-g2fq-wjrj

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality
LOW
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-601

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card