CVE-2026-27738: Angular SSR has an Open Redirect via X-Forwarded-Prefix
An Open Redirect vulnerability exists in the internal URL processing logic in Angular SSR. 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 (e.g., ///evil.com).
1. The application processes a redirect (e.g., from a router redirectTo or i18n locale switch). 2. Angular receives ///evil.com as the prefix. 3. It strips one slash, leaving //evil.com. 4. The resulting string is used in the Location header. 5. Modern browsers interpret // as a protocol-relative URL, redirecting the user from https://your-app.com to https://evil.com.
Impact This vulnerability allows attackers to conduct large-scale phishing and SEO hijacking: - Scale: A single request can poison a high-traffic route, impacting all users until the cache expires. - SEO Poisoning: Search engine crawlers may follow and index these malicious redirects, causing the legitimate site to be delisted or associated with malicious domains. - Trust: Because the initial URL belongs to the trusted domain, users and security tools are less likely to flag the redirect as malicious.
Attack Preconditions
- 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. - The cache must not vary on the X-Forwarded-Prefix header.
Patches - 21.2.0-rc.1 - 21.1.5 - 20.3.17 - 19.2.21
Workarounds Until the patch is applied, developers should sanitize the X-Forwarded-Prefix header in theirserver.ts before the Angular engine processes the request:
ts app.use((req, res, next) => { const prefix = req.headers['x-forwarded-prefix']?.trim(); if (prefix) { // Sanitize by removing all leading slashes req.headers['x-forwarded-prefix'] = prefix.replace(/^[/\\]+/, '/'); } next(); });
Resources - Report - Fix
Other sources
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 theirserver.ts before the Angular engine processes the request.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-27738?
CVE-2026-27738 is categorized as a medium severity vulnerability due to its potential to lead to open redirects.
How do I fix CVE-2026-27738?
To remediate CVE-2026-27738, upgrade to version 19.2.21 or higher for @angular/ssr.
Which versions are affected by CVE-2026-27738?
CVE-2026-27738 affects @angular/ssr versions prior to 19.2.21, 20.3.17, and 21.1.5.
What is the nature of the vulnerability in CVE-2026-27738?
CVE-2026-27738 involves an Open Redirect vulnerability due to improper handling of URL segments.
Is CVE-2026-27738 specific to any framework?
Yes, CVE-2026-27738 specifically affects Angular Server-Side Rendering (SSR) applications.