CVE-2026-111752

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: 1.0% (62nd 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
Elevated

Also known asEUVD-2026-116374 (ENISA EUVD) · GHSA-62vg-58rm-qff7 (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 8.2Exploit: No code on recordExposed 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.33, 21.2.25, and 22.2.1, @angular/router in Node.js server-side rendering fails to require auxiliary outlet URL segments to match routes configured for their outlet names. Crafted requests containing multiple unconfigured empty-path outlet groups can repeatedly evaluate the route configuration, construct duplicate ActivatedRouteSnapshot trees, execute canMatch guards and resolvers, and copy route parameters and queryParams for each outlet. An unauthenticated remote attacker can exhaust the Node.js heap or CPU and terminate an SSR worker when SSR is enabled, a route level contains an empty-path route or named outlet, upstream infrastructure forwards the request target, and the worker has a constrained heap. The allocation is transient rather than a persistent leak, and client-side SPAs and build-time prerendering are not affected. This issue is fixed in versions 20.3.33, 21.2.25, and 22.2.1.

CVSS
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
53
EG Risk 53/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
1.0%
EPSS %ILE
62nd
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
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

October 20, 2026

Last Modified

November 12, 2026

Advisory Details (10)

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

22.2.1

Patch available: angular/angular v22.2.1

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

21.2.25

Patch available: angular/angular v21.2.25

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

20.3.33

Patch available: angular/angular v20.3.33

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

commit e9bf52aa03a3 (angular/angular)

Patch available: angular/angular v22.2.1 (contains commit e9bf52aa03a3)

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

commit b0d2ba0f54e2 (angular/angular)

Patch available: angular/angular v20.3.33 (contains commit b0d2ba0f54e2)

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

commit a83f8119acd4 (angular/angular)

Patch available: angular/angular v21.2.25 (contains commit a83f8119acd4)

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

fix(router): require outlets to match a route before processing child…

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

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

Angular Router zero-segment group replay can create duplicate outlet siblings and exhaust SSR workers · Issue #70997 · angular/angular · GitHub

https://github.com/angular/angular/issues/70997
Web page

Angular Router auxiliary outlets can exhaust memory during SSR · Issue #70932 · angular/angular · GitHub

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

Denial of Service via Unmatched Empty-Path Outlet Route Matching in Server-Side Rendering (SSR) · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-62vg-58rm-qff7

Vendor Advisories for CVE-2026-111752(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.1 (fixes >= 22.0.0, < 22.2.1)—ghsa
npm@angular/router @ 21.2.25 (fixes >= 21.0.0, < 21.2.25)—ghsa
npm@angular/router @ 20.3.33 (fixes >= 20.0.0, < 20.3.33)—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.1: fixed in 22.2.1
  • 21.0.0 up to 21.2.25: fixed in 21.2.25
  • 20.0.0 up to 20.3.33: fixed in 20.3.33
  • 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 12× in last 7d / 19× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 20:28 UTCEchelonGraph re-scored
  2. 2026-11-12 20:28 UTCGHSA enrichmentGHSA-62vg-58rm-qff7 · GitHub severity HIGH
  3. 2026-11-12 16:33 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  4. 2026-11-11 16:38 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  5. 2026-11-11 03:33 UTCEchelonGraph re-scored
  6. 2026-11-11 03:33 UTCGHSA enrichmentGHSA-62vg-58rm-qff7 · GitHub severity HIGH
  7. 2026-11-10 16:42 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  8. 2026-11-09 16:42 UTCEchelonGraph re-scored
  9. 2026-11-09 16:42 UTCGHSA enrichmentGHSA-62vg-58rm-qff7 · GitHub severity HIGH
  10. 2026-11-09 16:34 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  11. 2026-11-09 16:28 UTCEchelonGraph re-scored
  12. 2026-11-09 16:28 UTCGHSA enrichmentGHSA-62vg-58rm-qff7 · GitHub severity HIGH
  13. 2026-11-09 15:55 UTCEchelonGraph re-scored
  14. 2026-11-09 15:55 UTCGHSA enrichmentGHSA-62vg-58rm-qff7 · GitHub severity HIGH
  15. 2026-11-08 16:38 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  16. 2026-11-07 16:38 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  17. 2026-11-06 16:36 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  18. 2026-11-05 16:36 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  19. 2026-11-04 16:34 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  20. 2026-11-03 22:12 UTCENISA EUVD ID recordedEUVD-2026-116374 · Source: ENISA EUVD
  21. 2026-11-03 21:27 UTCEchelonGraph re-scored
  22. 2026-11-03 21:27 UTCGHSA enrichmentGHSA-62vg-58rm-qff7 · GitHub severity HIGH
  23. 2026-11-03 21:01 UTCEchelonGraph re-scoredFirst assessed: 8.2 HIGH
  24. 2026-11-03 21:01 UTCGHSA enrichmentGHSA-62vg-58rm-qff7 · GitHub severity HIGH
  25. 2026-11-03 21:01 UTCMITRE cvelistV5CVSS → 8.2 · CVSS v4 → 8.2
Show 3 more
  1. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-62vg-58rm-qff7 · GitHub severity HIGH
  2. 2026-10-25 14:52 UTCEchelonGraph re-scored
  3. 2026-10-20 15:20 UTCEchelonGraph re-scored

Related CVEs(same product + same CWE)

Same product

2 shown

npm:@angular/router

Frequently asked(5)

What is CVE-2026-111752?
CVE-2026-111752 is a high-severity vulnerability; its CVE record was published on October 20, 2026. Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.33, 21.2.25, and 22.2.1, @angular/router in Node.js server-side rendering fails to require auxiliary outlet URL segments to match routes configured for…
When was the CVE record for CVE-2026-111752 published?
The CVE record for CVE-2026-111752 was published on October 20, 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 November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-111752 actively exploited?
CVE-2026-111752 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-111752?
CVE-2026-111752 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-111752?
A fix for CVE-2026-111752 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-111752 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-111752

Explore →

Is Your Infrastructure Affected by CVE-2026-111752?

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

Book a Demo →Browse All CVEs