CVE-2026-27738

Angular SSR has an Open Redirect via X-Forwarded-Prefix

MEDIUM
6.9
CVSS Score
Published: February 25, 2026 at 04:40 PM UTC
Updated: June 17, 2026 at 10:27 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.9
Exploit prediction
EPSS 0.4%
SSVC
PoC

Description

The Angular SSR is a server-rise rendering tool for Angular applications. An Open Redirect vulnerability exists in the internal URL processing logic in versions on the 19.x branch prior to 19.2.21, the 20.x branch prior to 20.3.17, and the 21.x branch prior to 21.1.5 and 21.2.0-rc.1. The logic normalizes URL segments by stripping leading slashes; however, it only removes a single leading slash. When an Angular SSR application is deployed behind a proxy that passes the `X-Forwarded-Prefix` header, an attacker can provide a value starting with three slashes. This vulnerability allows attackers to conduct large-scale phishing and SEO hijacking. In order to be vulnerable, the application must use Angular SSR, the application must have routes that perform internal redirects, the infrastructure (Reverse Proxy/CDN) must pass the `X-Forwarded-Prefix` header to the SSR process without sanitization, and the cache must not vary on the `X-Forwarded-Prefix` header. Versions 21.2.0-rc.1, 21.1.5, 20.3.17, and 19.2.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 < 19.2.21v < 20.3.17v < 21.1.5v < 21.2.0-rc.0
Affected range stops below 19.2.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2.0-rc.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCPoCAutomatablePartial impact

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

CVSS

6.9MEDIUMGitHub_M
Vector?

Quick Info

StatusDEFERRED
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