CVE-2026-101896

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9% (59th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-101147 (ENISA EUVD) · GHSA-ff3f-86qr-9cv3 (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 30, 2026

Last Modified

October 20, 2026

Advisory Details (9)

Auto-updated Oct 14, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

22.2.0

Patch available: angular/angular v22.2.0

https://github.com/angular/angular/releases/tag/v22.2.0
GitHub release Patch Available

21.2.24

Patch available: angular/angular v21.2.24

https://github.com/angular/angular/releases/tag/v21.2.24
GitHub release Patch Available

20.3.32

Patch available: angular/angular v20.3.32

https://github.com/angular/angular/releases/tag/v20.3.32
GitHub commit Patch Available

commit ddfe21072ba3 (angular/angular)

Patch available: angular/angular v20.3.32 (contains commit ddfe21072ba3)

https://github.com/angular/angular/commit/ddfe21072ba32ca4cd9d7d3c6b7df66af81d58c4
GitHub commit Patch Available

commit 5af61216eab8 (angular/angular)

Patch available: angular/angular v22.2.0 (contains commit 5af61216eab8)

https://github.com/angular/angular/commit/5af61216eab8bf4a6697a1d79bda3d857c06f89d
GitHub commit Patch Available

commit 03872a80bcf1 (angular/angular)

Patch available: angular/angular v21.2.24 (contains commit 03872a80bcf1)

https://github.com/angular/angular/commit/03872a80bcf1c89b2b04cdd3f444b2ee954da583
GitHub pull request Patch Available

fix(router): avoid dense elements allocation for numeric URL keys

Patch available: angular/angular v22.3.0-next.0 (PR #70717 merged 2026-09-23)

https://github.com/angular/angular/pull/70717
Web page

Angular Router numeric matrix parameters can exhaust memory during SSR · Issue #70716 · angular/angular · GitHub

https://github.com/angular/angular/issues/70716
GitHub advisoryMentions a patch (unverified)

Denial of Service via Numeric URL Matrix Parameters in Server-Side Rendering (SSR) · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-ff3f-86qr-9cv3

Vendor Advisories for CVE-2026-101896(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@angular/router @ 22.2.0 (fixes >= 22.0.0, < 22.2.0)—ghsa
npm@angular/router @ 21.2.24 (fixes >= 21.0.0, < 21.2.24)—ghsa
npm@angular/router @ 20.3.32 (fixes >= 20.0.0, < 20.3.32)—ghsa
npm@angular/router—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@angular/router—
  • 22.0.0 up to 22.2.0: fixed in 22.2.0
  • 21.0.0 up to 21.2.24: fixed in 21.2.24
  • 20.0.0 up to 20.3.32: fixed in 20.3.32
  • every version through 19.2.25: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-ff3f-86qr-9cv3 · GitHub severity HIGH
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  8. 2026-10-27 20:35 UTCEG score recompute
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  12. 2026-10-25 14:57 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-22 11:34 UTCEG score recompute
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-10-20 02:26 UTCEG score recompute
  20. 2026-10-20 01:54 UTCEG score recompute
  21. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  22. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-18 05:11 UTCEG score recompute
  24. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.7% · 51st percentile
Show 10 more
  1. 2026-10-16 16:09 UTCEG score recompute
  2. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  3. 2026-10-14 17:13 UTCEG score recompute
  4. 2026-10-14 15:27 UTCEG score recomputeFirst assessed: 8.2 HIGH
  5. 2026-10-14 15:24 UTCMITRE cvelistV5CVSS v3 → 8.2 · CVSS v4 → 8.2
  6. 2026-10-12 16:41 UTCEG score recompute
  7. 2026-10-11 20:16 UTCEG score recompute
  8. 2026-10-11 18:28 UTCEG score recompute
  9. 2026-10-11 15:02 UTCEG score recompute
  10. 2026-09-30 16:12 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-101896?
CVE-2026-101896 is a high-severity vulnerability; its CVE record was published on September 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…
When was the CVE record for CVE-2026-101896 published?
The CVE record for CVE-2026-101896 was published on September 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-101896 actively exploited?
CVE-2026-101896 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101896?
CVE-2026-101896 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101896?
A fix for CVE-2026-101896 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-101896 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-101896

Explore →

Is Your Infrastructure Affected by CVE-2026-101896?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs