Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

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

CVE-2026-101896GHSA-ff3f-86qr-9cv3

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @angular/router

    Affected
    >= 22.0.0, < 22.2.0>= 21.0.0, < 21.2.24>= 20.0.0, < 20.3.32<= 19.2.25
    Fixed in
    22.2.0, 20.3.32, 21.2.24

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.2 · 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 · score source
EPSS
  • CVE-2026-101896: 0.91% estimated exploitation activity in the next 30 days; percentile 60.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 (HOLEYELEMENTS) 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-ff3f-86qr-9cv3

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-ff3f-86qr-9cv3

  4. Revision 1 · created ·

    Published from ghsa record GHSA-ff3f-86qr-9cv3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-101896

Advisory: Angular Server-Side Rendering (SSR): Denial of Service via Numeric URL Matrix Parameters
IDs: CVE-2026-101896, GHSA-ff3f-86qr-9cv3
Record: https://patchnext.com/advisories/cve-2026-101896 (revision 4, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: @angular/router 22.2.0, 21.2.24, 20.3.32. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @angular/router: affected >= 22.0.0, < 22.2.0; >= 21.0.0, < 21.2.24; >= 20.0.0, < 20.3.32; <= 19.2.25; fixed in 22.2.0, 20.3.32, 21.2.24

## Suggested inspection (read-only)
- `npm ls @angular/router --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @angular/router.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-ff3f-86qr-9cv3 (GitHub-reviewed advisory GHSA-ff3f-86qr-9cv3 lists affected ranges: npm @angular/router >=22.0.0 =21.0.0 =20.0.0 =0 <=19.2.25)
- Verified: https://osv.dev/vulnerability/GHSA-ff3f-86qr-9cv3 (OSV record GHSA-ff3f-86qr-9cv3 lists affected ranges: npm @angular/router >=22.0.0 =21.0.0 =20.0.0 =0 <=19.2.25)

Commands are suggestions: review each one before running it.

Loading voting…