Skip to content
Fencer Intel
high 8.2

CVE-2026-111752 json

Angular: Denial of Service via Unmatched Empty-Path Outlet Route Matching in Server-Side Rendering (SSR)

published 20d ago modified 10h ago also EUVD-2026-116374 , GHSA-62vg-58rm-qff7

cvss
8.2
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm @angular/router 20.3.33, 21.2.25, 22.2.1

Is CVE-2026-111752 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-111752 updated cvss 7.5

@angular/router: @angular/router: Denial of Service via improper route outlet matching in Server-Side Rendering

  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/volsync-rhel9, rhacm2/volsync-operator-bundle Red Hat Enterprise Linux 7 firefox, firefox 140.17.0-1.el10_2 Red Hat Enterprise Linux 8 firefox, mozjs60, thunderbird, firefox 140.17.0-1.el10_2, thunderbird 140.17.0-1.el10_0, dotnet5.0-build-reference-packages 0-12.20211117git6ce5818.el8_5 Red Hat Enterprise Linux 9 firefox, librbd1, librados2, firefox-x11, thunderbird, gjs 1.80.2-11.el10, +2 more Red Hat Enterprise Linux 10 ceph 18.2.1-4.el10, gjs 1.80.2-11.el10, firefox 140.17.0-1.el10_2, thunderbird 140.17.0-1.el10_0 Red Hat Fuse 7 redhat-fuse-sources.zip 7.13.0, redhat-fuse-maven-repository.zip 7.13.0
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
10h ago

Exploit prediction

0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/angular/angular/security/advisories/GHSA-62vg-58rm-qff7 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 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
CNA 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
npm @angular/router
>=22.0.0, <22.2.1
>=21.0.0, <21.2.25
>=20.0.0, <20.3.33
<=19.2.25
22.2.1
21.2.25
20.3.33

Affected products

  • angular angular

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-405 Asymmetric Resource Consumption (Amplification)

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.