Angular: Denial of Service via Numeric URL Matrix Parameters in Server-Side Rendering (SSR)

Summary

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.

Timeline

1. Oct 14, 2026, 3:05 PM UTCCVE published
2. Oct 20, 2026, 1:32 AM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Oct 20, 2026, 1:32 AM UTCRecord last updated

Affected versions

• angular angular

  through 19.2.25; From 20.0.0 · fixed in 20.3.32; From 21.0.0 · fixed in 21.2.24; From 22.0.0 · fixed in 22.2.0

• @angular router

  through 19.2.25; From 20.0.0 · fixed in 20.3.32; From 21.0.0 · fixed in 21.2.24; From 22.0.0 · fixed in 22.2.0

• @angular/routernpm

  From 22.0.0 · fixed in 22.2.0

• @angular/routernpm

  From 21.0.0 · fixed in 21.2.24

• @angular/routernpm

  From 20.0.0 · fixed in 20.3.32

• @angular/routernpm

  through 19.2.25

References 9