CVE-2026-101896: Angular Server-Side Rendering (SSR) Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-ff3f-86qr-9cv3
CWE-400 CWE-770
Published
Advisory Summary

CVE-2026-101896 is a HIGH denial of service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Angular Server-Side Rendering (SSR) libraries in the npm ecosystem. The issue involves denial of service via numeric url matrix parameters. Remediation is available by upgrading affected packages to version 22.2.0, 21.2.24, 20.3.32.

CVE-2026-101896 at a Glance

CVE Identifier CVE-2026-101896
GHSA Identifier GHSA-ff3f-86qr-9cv3
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product Angular Server-Side Rendering (SSR)
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-101896

To remediate this vulnerability, upgrade all affected Angular Server-Side Rendering (SSR) dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@angular/router fixed: 22.2.0
npm install @angular/router@22.2.0
@angular/router fixed: 21.2.24
npm install @angular/router@21.2.24
@angular/router fixed: 20.3.32
npm install @angular/router@20.3.32
@angular/router fixed: Latest secure release
npm install @angular/router@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @angular/router

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-101896, inspect your project dependencies using npm:

npm ls @angular/router

Analyze the terminal output to locate any version of Angular Server-Side Rendering (SSR) in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 22.2.0), your application is affected.

Note: The npm ls @angular/router command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Angular Server-Side Rendering (SSR), software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

A denial of service (DoS) vulnerability was identified in `@angular/router` when Server-Side Rendering (SSR) is enabled on Node.js (V8). When `@angular/router` parses incoming request URLs, it extracts path segments, matrix parameters, and child outlets into plain JavaScript objects (`Record<string, string>`). When matrix parameter names or outlet names are numeric strings (such as `/a;990;2522`), the V8 JavaScript engine interprets them as array-indexed properties rather than named properties. Under V8's internal property-storage heuristics, setting numeric keys on an initially empty object causes V8 to allocate a dense array backing store (`HOLEY_ELEMENTS`) sized to the maximum index rather than falling back to sparse dictionary storage. Specifically, assigning sequential or moderately large numeric keys (like `990` followed by `2522`) causes V8 to allocate a contiguous backing store of ~2,522 pointers (~20 KB to 25 KB of heap) for a single 11-byte segment. Because each segment in a URL path allocates its own independent `parameters` object, an attacker can craft URLs with repeated numeric matrix parameters to achieve an asymmetric memory amplification factor of approximately **~350x**. ### Impact Successful exploitation allows an unauthenticated remote attacker to exhaust the Node.js old-space heap with modest request volume, terminating the SSR worker with an unrecoverable `JavaScript heap out of memory` fatal error and causing a Denial of Service. * **High Amplification:** A single 11-byte segment (`/a;990;2522`) consumes ~20 KB–25 KB of V8 heap. * **Low Concurrency Required:** * With 8 KB request paths (~740 segments, within default Nginx 8 KB buffer limits), as few as **12–22 concurrent requests** crash a 256 MiB–512 MiB Node.js SSR worker. * With smaller 1 KB–2 KB request paths (~90–180 segments), a burst of ~50–100 concurrent requests achieves the same heap exhaustion. * **Client-side SPAs Unaffected:** Pure client-side Angular applications (Single Page Applications without SSR) are **not** vulnerable, as local browser memory consumption does not cross a security boundary. ### Attack Preconditions & Vulnerable Configurations An application is affected only if **all** of the following conditions are met: * **SSR Enabled:** The application runs in a Server-Side Rendering environment powered by Node.js / V8. * **Direct Router Parsing:** User-controlled request URLs are parsed by `@angular/router` during SSR. * **No Reverse-Proxy Semicolon/Segment Filtering:** Upstream reverse proxies (Nginx, Cloudflare, ALB) forward URLs containing semicolons (`;`) and multiple path segments without stripping or rejecting them. #### Exploit Payload Example An attacker sends concurrent HTTP requests with repeated numeric matrix parameters: ```http GET /a;990;2522/a;990;2522/a;990;2522/... HTTP/1.1 Host: example.com ``` Even with paths under 2 KB, overlapping requests during SSR will rapidly consume the V8 heap until the process crashes. ### Patches The issue is resolved by updating `@angular/router` to enforce V8 dictionary elements storage (`setUrlDerivedKey`) for numeric URL-derived keys (index >= 32). This prevents V8 from allocating oversized contiguous array backing stores while preserving route matching, parameter values, and component input bindings. * `22.2.0` * `21.2.24` * `20.3.32` ### Workarounds & Mitigations If you cannot immediately upgrade to a patched version, apply one of the following mitigations at your edge or reverse proxy: 1. **Block or Sanitize Matrix Parameters at the Reverse Proxy:** Configure your reverse proxy (e.g., Nginx, Cloudflare, or AWS WAF) to reject or strip semicolons (`;`) in request paths before forwarding requests to the Angular SSR service: ```nginx # Nginx example: reject requests containing matrix parameters if ($uri ~* ";") { return 400; } ``` 2. **Enforce Strict Path Segment Limits:** Reject requests with excessive path depth (e.g., more than 20–30 segments). 3. **Increase Node.js Old Space:** Increase `--max-old-space-size` (e.g., to 2048 or 4096 MB) to increase the concurrency threshold required to exhaust memory, though this does not fully eliminate the vulnerability under sustained traffic.

CVE-2026-101896 Affected Angular Server-Side Rendering (SSR) Versions

4 component(s)
Fixed Versions:
22.2.021.2.2420.3.32
Product / Package Ecosystem Affected Versions Fixed Version
@angular/router
npm
≥ 22.0.0
< 22.2.0
22.2.0
@angular/router
npm
≥ 21.0.0
< 21.2.24
21.2.24
@angular/router
npm
≥ 20.0.0
< 20.3.32
20.3.32
@angular/router
npm
≤ 19.2.25

References

Frequently Asked Questions

What is CVE-2026-101896?
CVE-2026-101896 is a security vulnerability in Angular Server-Side Rendering (SSR) involving Denial of Service via Numeric URL Matrix Parameters under CWE-400: Uncontrolled Resource Consumption.
Which Angular Server-Side Rendering (SSR) versions are affected?
Affected versions include releases prior to 22.2.0, 21.2.24, 20.3.32 across affected packages: @angular/router.
What version fixes CVE-2026-101896?
Upgrading to 22.2.0, 21.2.24, 20.3.32 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @angular/router affected?
Yes, @angular/router is affected in releases prior to 22.2.0, 21.2.24, 20.3.32, Latest secure release. Upgrade your dependency to 22.2.0, 21.2.24, 20.3.32, Latest secure release or later.
What CWE is associated with CVE-2026-101896?
CVE-2026-101896 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check npm dependencies for CVE-2026-101896?
Run the dependency tree command: 'npm ls @angular/router'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-ff3f-86qr-9cv3",
  "modified" : "2026-09-30T15:40:47Z",
  "published" : "2026-09-30T15:40:47Z",
  "aliases" : [ "CVE-2026-101896" ],
  "summary" : "Angular Server-Side Rendering (SSR): Denial of Service via Numeric URL Matrix Parameters",
  "details" : "A denial of service (DoS) vulnerability was identified in `@angular/router` when Server-Side Rendering (SSR) is enabled on Node.js (V8).\n\nWhen `@angular/router` parses incoming request URLs, it extracts path segments, matrix parameters, and child outlets into plain JavaScript objects (`Record<string, string>`). When matrix parameter names or outlet names are numeric strings (such as `/a;990;2522`), the V8 JavaScript engine interprets them as array-indexed properties rather than named properties.\n\nUnder V8's internal property-storage heuristics, setting numeric keys on an initially empty object causes V8 to allocate a dense array backing store (`HOLEY_ELEMENTS`) sized to the maximum index rather than falling back to sparse dictionary storage. Specifically, assigning sequential or moderately large numeric keys (like `990` followed by `2522`) causes V8 to allocate a contiguous backing store of ~2,522 pointers (~20 KB to 25 KB of heap) for a single 11-byte segment.\n\nBecause each segment in a URL path allocates its own independent `parameters` object, an attacker can craft URLs with repeated numeric matrix parameters to achieve an asymmetric memory amplification factor of approximately **~350x**.\n\n### Impact\n\nSuccessful exploitation allows an unauthenticated remote attacker to exhaust the Node.js old-space heap with modest request volume, terminating the SSR worker with an unrecoverable `JavaScript heap out of memory` fatal error and causing a Denial of Service.\n\n* **High Amplification:** A single 11-byte segment (`/a;990;2522`) consumes ~20 KB–25 KB of V8 heap.\n* **Low Concurrency Required:**\n  * With 8 KB request paths (~740 segments, within default Nginx 8 KB buffer limits), as few as **12–22 concurrent requests** crash a 256 MiB–512 MiB Node.js SSR worker.\n  * With smaller 1 KB–2 KB request paths (~90–180 segments), a burst of ~50–100 concurrent requests achieves the same heap exhaustion.\n* **Client-side SPAs Unaffected:** Pure client-side Angular applications (Single Page Applications without SSR) are **not** vulnerable, as local browser memory consumption does not cross a security boundary.\n\n### Attack Preconditions & Vulnerable Configurations\n\nAn application is affected only if **all** of the following conditions are met:\n\n* **SSR Enabled:** The application runs in a Server-Side Rendering environment powered by Node.js / V8.\n* **Direct Router Parsing:** User-controlled request URLs are parsed by `@angular/router` during SSR.\n* **No Reverse-Proxy Semicolon/Segment Filtering:** Upstream reverse proxies (Nginx, Cloudflare, ALB) forward URLs containing semicolons (`;`) and multiple path segments without stripping or rejecting them.\n\n#### Exploit Payload Example\n\nAn attacker sends concurrent HTTP requests with repeated numeric matrix parameters:\n\n```http\nGET /a;990;2522/a;990;2522/a;990;2522/... HTTP/1.1\nHost: example.com\n```\n\nEven with paths under 2 KB, overlapping requests during SSR will rapidly consume the V8 heap until the process crashes.\n\n### Patches\n\nThe issue is resolved by updating `@angular/router` to enforce V8 dictionary elements storage (`setUrlDerivedKey`) for numeric URL-derived keys (index >= 32). This prevents V8 from allocating oversized contiguous array backing stores while preserving route matching, parameter values, and component input bindings.\n\n* `22.2.0`\n* `21.2.24`\n* `20.3.32`\n\n### Workarounds & Mitigations\n\nIf you cannot immediately upgrade to a patched version, apply one of the following mitigations at your edge or reverse proxy:\n\n1. **Block or Sanitize Matrix Parameters at the Reverse Proxy:**  \n   Configure your reverse proxy (e.g., Nginx, Cloudflare, or AWS WAF) to reject or strip semicolons (`;`) in request paths before forwarding requests to the Angular SSR service:\n   ```nginx\n   # Nginx example: reject requests containing matrix parameters\n   if ($uri ~* \";\") {\n       return 400;\n   }\n   ```\n2. **Enforce Strict Path Segment Limits:**  \n   Reject requests with excessive path depth (e.g., more than 20–30 segments).\n3. **Increase Node.js Old Space:**  \n   Increase `--max-old-space-size` (e.g., to 2048 or 4096 MB) to increase the concurrency threshold required to exhaust memory, though this does not fully eliminate the vulnerability under sustained traffic.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/router"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "22.0.0"
      }, {
        "fixed" : "22.2.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/router"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "21.0.0"
      }, {
        "fixed" : "21.2.24"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/router"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "20.0.0"
      }, {
        "fixed" : "20.3.32"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/router"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "19.2.25"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/security/advisories/GHSA-ff3f-86qr-9cv3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/issues/70716"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/pull/70717"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/03872a80bcf1c89b2b04cdd3f444b2ee954da583"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/5af61216eab8bf4a6697a1d79bda3d857c06f89d"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/ddfe21072ba32ca4cd9d7d3c6b7df66af81d58c4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/angular/angular"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400", "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-30T15:40:47Z",
    "nvd_published_at" : null
  }
}