Answer in brief
CVE-2026-111752 records a High severity (CVSS 8.2) vulnerability in Angular: Denial of Service via Unmatched Empty-Path Outlet Route Matching in Server-Side Rendering (SSR). The current sources do not mark it as known exploited. The current feed maps angular/angular (generic), @angular/router (npm), @angular/router (npm), @angular/router (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps angular/angular (generic), @angular/router (npm), @angular/router (npm), @angular/router (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| angular/angulargeneric | <=19.2.25 || >=20.0.0 <20.3.33 || >=21.0.0 <21.2.25 || >=22.0.0 <22.2.1 | = 19.2.25, 20.3.33, 21.2.25, 22.2.1 |
| @angular/routernpm | <=19.2.25 | Not reported |
| @angular/routernpm | >=21.0.0,<21.2.25 | 21.2.25 |
| @angular/routernpm | >=22.0.0,<22.2.1 | 22.2.1 |
| @angular/routernpm | >=20.0.0,<20.3.33 | 20.3.33 |
| @angular/routernpm | >=22.0.0 <22.2.1 | 22.2.1 |
| @angular/routernpm | >=21.0.0 <21.2.25 | 21.2.25 |
| @angular/routernpm | >=20.0.0 <20.3.33 | 20.3.33 |
| @angular/routernpm | >=0 | Not reported |
Published upstream
Nov 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 20, 2026
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.33, 21.2.25, and 22.2.1, @angular/router in Node.js server-side rendering fails to require auxiliary outlet URL segments to match routes configured for their outlet names. Crafted requests containing multiple unconfigured empty-path outlet groups can repeatedly evaluate the route configuration, construct duplicate ActivatedRouteSnapshot trees, execute canMatch guards and resolvers, and copy route parameters and queryParams for each outlet. An unauthenticated remote attacker can exhaust the Node.js heap or CPU and terminate an SSR worker when SSR is enabled, a route level contains an empty-path route or named outlet, upstream infrastructure forwards the request target, and the worker has a constrained heap. The allocation is transient rather than a persistent leak, and client-side SPAs and build-time prerendering are not affected. This issue is fixed in versions 20.3.33, 21.2.25, and 22.2.1.
Quoted source text, attributed separately from HOL analysis.