All vulnerabilities

Servers and applications

CVE-2026-111752

Denial of Service via Unmatched Empty-Path Outlet Route Matching in Server-Side Rendering (SSR)

Severity
High 8.2
Published
30 Sept 2026
Last changed
9 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 63% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Uncontrolled resource consumption (CWE-400)CWE-405
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Take it down
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Also known as
GHSA-62vg-58rm-qff7
Sources
CVE Program, Project advisories (GitHub)

Description

A denial of service (DoS) vulnerability was identified in @angular/router when Server-Side Rendering (SSR) is enabled on Node.js (V8).

During route recognition, @angular/router fails to validate whether an auxiliary outlet segment in the URL matches a route configured for that specific outlet name. Because unconfigured empty-path outlet groups (such as a:/(), x:/(...), or ///(...)) are not rejected during matching, the router repeatedly re-evaluates the route configuration against each arbitrary outlet segment provided in the URL.

When a request URL contains multiple arbitrary empty-path outlet segments, this improper matching forces the router to instantiate duplicate ActivatedRouteSnapshot trees, repeatedly execute canMatch guards and route resolvers, and allocate separate copies of route parameters and queryParams for each unconfigured outlet.

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

Workarounds

If you cannot immediately upgrade to a patched version, apply one or more of the following mitigations:

  • Reject Parenthesized or Empty-Path Outlet URLs in Middleware or WAF (Recommended): In @angular/router, auxiliary outlet groups in a URL always use parentheses (...), and empty-path outlet groups in a URL always take the form :/( , (/ , or ///( .
  • If your application does not use named (auxiliary) outlets in URLs, reject requests whose path contains ( or ) before Angular SSR handles the request.
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