Answer in brief
CVE-2026-101896 records a High severity (CVSS 8.2) vulnerability in Angular: Denial of Service via Numeric URL Matrix Parameters in Server-Side Rendering (SSR). The current sources do not mark it as known exploited. The current feed maps angular/angular (generic), @angular/router (generic), @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 (generic), @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.32 || >=21.0.0 <21.2.24 || >=22.0.0 <22.2.0 | = 19.2.25, 20.3.32, 21.2.24, 22.2.0 |
| @angular/routergeneric | <=19.2.25 || >=20.0.0 <20.3.32 || >=21.0.0 <21.2.24 || >=22.0.0 <22.2.0 | = 19.2.25, 20.3.32, 21.2.24, 22.2.0 |
| @angular/routernpm | >=22.0.0,<22.2.0 | 22.2.0 |
| @angular/routernpm | >=21.0.0,<21.2.24 | 21.2.24 |
| @angular/routernpm | >=20.0.0,<20.3.32 | 20.3.32 |
| @angular/routernpm | <=19.2.25 | Not reported |
| @angular/routernpm | >=22.0.0 <22.2.0 | 22.2.0 |
| @angular/routernpm | >=21.0.0 <21.2.24 | 21.2.24 |
| @angular/routernpm | >=20.0.0 <20.3.32 | 20.3.32 |
| @angular/routernpm | >=0 | Not reported |
Published upstream
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 30, 2026
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.32, 21.2.24, and 22.2.0, the @angular/router URL parser stores numeric matrix parameter names and numeric outlet names as properties on initially empty JavaScript objects during Node.js server-side rendering. V8 can interpret these URL-derived keys as array indices and allocate dense backing stores sized to high numeric values, so repeated small path segments cause disproportionate per-segment heap consumption. An unauthenticated attacker can send overlapping requests containing repeated numeric matrix parameters when SSR is enabled, the router directly parses the request URL, and upstream proxies allow semicolons and multiple path segments, eventually exhausting the Node.js old-space heap and terminating the SSR worker. Pure client-side Angular applications are not affected. This issue is fixed in versions 20.3.32, 21.2.24, and 22.2.0.
Quoted source text, attributed separately from HOL analysis.