All vulnerabilities

Servers and applications

CVE-2026-111754

Open Redirect via Protocol-Relative URLs in Server-Side Rendering (SSR)

Severity
Medium 5.1
Published
30 Sept 2026
Last changed
3 Nov 2026
Added to UpHeron
3 Nov 2026
Fixed in
20.3.33, 21.2.25, 22.2.1
Exploit chance
1% in the next 30 daysHigher than 62% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Open redirect (CWE-601)
Attack
Over the network · No login needed · Needs someone to click or open something
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Also known as
GHSA-w739-gvwx-grc3
Sources
CVE Program, Project advisories (GitHub)

Description

An open redirect vulnerability was identified in @angular/platform-server when Server-Side Rendering (SSR) is enabled.

When Angular SSR renders an incoming request, URL resolution and platform navigation are managed by ServerPlatformLocation using resolveUrl (or parseUrl in v20). While resolveUrl rejected protocol-relative URLs whose raw string directly started with //, this check ran prior to WHATWG URL normalization.

When a request URL includes a popping dot-segment followed by multiple slashes (such as /.//evil.test or serialized from router route shapes like /.;/(//evil.test)), the input bypassed the initial urlStr.startsWith('//') check. Subsequent WHATWG URL parsing resolved the dot-segments and resulted in a pathname starting with // (//evil.test).

Consequently, ServerPlatformLocation stored pathname = '//evil.test'. When @angular/ssr detected a mismatch between the rendered URL and the router's final location state, it emitted the unnormalized pathname into the HTTP…

From angular/angular's security advisory. Shortened; the full text is there.

Workarounds

If you cannot immediately upgrade to a patched version, apply one of the following mitigations at your edge reverse proxy or WAF:

  • Reject Paths with Dot-Segments Followed by Slashes: Configure your reverse proxy (e.g., Nginx, Cloudflare, AWS WAF) to block requests containing /.//, /..//, or /.;/:
  • Sanitize Redirect Headers: Ensure edge proxies or API gateways rewrite or disallow protocol-relative (//) Location response headers originating from the SSR upstream.
Workarounds as given by angular/angular's security advisory.

Affected software

SoftwareAffected versions
AngularServers and applications · cna:angular|angular
  • Every version up to 19.2.25
  • From 20.0.0 before 20.3.33
  • From 21.0.0 before 21.2.25
  • From 22.0.0 before 22.2.1
AngularServers and applications · github:angular/angular
  • Every version up to 19.2.25
  • From 20.0.0 before 20.3.33
  • From 21.0.0 before 21.2.25
  • From 22.0.0 before 22.2.1

About Angular

web application framework

From Wikidata, CC0 1.0.
Developers who used it in the past year
18.2%Stack Overflow Developer Survey 2025, 2025
Weekly downloads (npm)
8,195,583npm, 15 Nov 2026
GitHub stars
101,504GitHub, 15 Nov 2026
Forks
28,216GitHub, 15 Nov 2026
Latest release
v22.2.6GitHub, 15 Nov 2026
Released
12 Nov 2026GitHub
Developer
GoogleWikidata
License
MIT LicenseWikidata
Written in
TypeScriptWikidata
First released
15 Sept 2016Wikidata
First published on GitHub
18 Sept 2014GitHub

Release lines

ReleaseLatestSecurity fixes
2222.2.6Until 30 Jun 2028
2121.2.26Until 30 Jun 2027
2020.3.35Until 28 Nov 2026
1919.2.25Ended 19 May 2026
1818.2.14Ended 21 Nov 2025
1717.3.12Ended 15 May 2025

From endoflife.date.

References