@angular/platform-server: Open Redirect via Protocol-Relative URLs in Server-Side Rendering (SSR) (CVE-2026-111754)
Description
An open redirect vulnerability exists in @angular/platform-server when Server-Side Rendering (SSR) is enabled. The vulnerability arises from improper URL normalization allowing crafted URLs with dot-segments and multiple slashes to bypass checks and cause the server to emit a protocol-relative redirect in the HTTP Location header. This can redirect users to arbitrary external domains. Pure client-side Angular applications without SSR are not affected. The issue is fixed in versions 22.2.1, 21.2.25, and 20.3.33.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in @angular/platform-server's SSR occurs because the URL resolution logic uses resolveUrl (or parseUrl in v20) which initially rejects protocol-relative URLs starting with '//' before WHATWG URL normalization. However, URLs containing dot-segments followed by multiple slashes (e.g., '/.//evil.test') bypass this initial check. After normalization, the pathname starts with '//evil.test', which is stored and later emitted in the Location header during a redirect. Browsers interpret this as a protocol-relative redirect to an external domain. This allows unauthenticated attackers to craft URLs that bypass application-level guards and cause SSR to redirect users off-origin. The vulnerability affects SSR-enabled Angular applications with parameterized routes and reverse proxies that do not normalize or strip semicolons or dot-segments. The issue is resolved by patching resolveUrl and parseUrl to verify the normalized pathname does not start with '//' when protocol-relative URLs are disallowed.
Potential Impact
An unauthenticated remote attacker can exploit this vulnerability to cause Angular SSR to issue HTTP 302 redirects to arbitrary external domains. This bypasses common application-level redirect allowlists that do not account for URL normalization bypasses. The redirect can lead users to malicious sites, potentially facilitating phishing or other attacks. Pure client-side Angular applications without SSR are not vulnerable. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix is available in @angular/platform-server versions 22.2.1, 21.2.25, and 20.3.33. Applications should upgrade to these versions to remediate the vulnerability. If immediate upgrade is not possible, mitigations include configuring edge reverse proxies or WAFs to reject requests containing suspicious path normalization sequences such as '/.//', '/..//', or '/.;/'. Additionally, proxies or API gateways should sanitize or disallow protocol-relative ('//') Location headers in HTTP responses originating from the SSR backend.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w739-gvwx-grc3
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-111754"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6ad7914c2cdf04f656405af8
Added to database: 10/20/2026, 16:05:32 UTC
Last enriched: 10/20/2026, 16:18:37 UTC
Last updated: 10/20/2026, 16:18:37 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.