ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-111752

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

Published Sep 30, 2026 · catalog updated Oct 19, 2026 · Denial of Service via

Last checked Nov 3, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-111752. A missing EPSS score is not a low risk. Compare Denial of Service via with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Denial of Service via).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Not in the current FIRST EPSS dataset
Remediation
Version ranges on file
Affected products
npm @angular/router

A denial of service (DoS) vulnerability was identified in when Server-Side Rendering (SSR) is enabled on Node.js (V8). During route recognition, fails to validate whether an auxiliary outlet segment in the URL matches a route configured for that specific outlet name. Because unconfigured empty-path outlet groups (such as , , or ) are not rejected during matching, the router repeatedly re-evaluates the route configuration against each arbitrary outlet segment provided in the URL. When a request URL contains multiple arbitrary empty-path outlet segments, this improper matching forces the router to instantiate duplicate trees, repeatedly execute guards and route resolvers, and allocate separate copies of route parameters and for each unconfigured outlet. An unauthenticated remote attacker can exploit this behavior by sending requests with crafted outlet segments to exhaust the Node.js memory heap or overwhelm CPU resources, leading to SSR worker termination and service disruption. ### Impact Successful exploitation allows an unauthenticated remote attacker to exhaust the Node.js heap with a single crafted request or a small number of concurrent requests, terminating the SSR worker process with a fatal JavaScript heap out-of-memory crash. When the matched routes declare guards or resolvers, a single short request can also trigger repeated guard or resolver executions, increasing load on backend services and holding worker connections open. * **Transient Allocation:** Memory is released once route recognition completes; there is no persistent memory leak. The primary impact is process termination. * **Client-side SPAs Unaffected:** Client-side Angular applications running in the browser are not vulnerable, as browser memory consumption does not cross a security boundary. * **Prerendering (SSG) Unaffected:** Build-time prerendering does not process attacker-supplied request URLs. ### Attack Preconditions & Vulnerable Configurations An application is affected only if all o

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm @angular/router<= 19.2.25
  • npm @angular/router>= 20.0.0, < 20.3.33
  • npm @angular/router>= 21.0.0, < 21.2.25
  • npm @angular/router>= 22.0.0, < 22.2.1

How to fix CVE-2026-111752

  • Upgrade

    CVE-2026-111752 lists a fix boundary at 19.2.25. Compare the installed build with that boundary before you change production.

  • Version check

    Affected <= 19.2.25

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2026-111752. A missing EPSS score is not a low risk. Compare Denial of Service via with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with <= 19.2.25, >= 20.0.0, < 20.3.33, >= 21.0.0, < 21.2.25, >= 22.0.0, < 22.2.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-400: Uncontrolled Resource Consumption; CWE-405. EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Angular security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 30, 2026 · Maintainer security tabs

    Detected

    A denial of service (DoS) vulnerability was identified in when Server-Side Rendering (SSR) is enabled on Node.js (V8). During route recognition, fails to validate whether an auxiliary outlet segment in the URL matches a route configured for that specific outlet name. Because unconfigured empty-path outlet groups (such as , , or ) are not rejected during matching, the router repeatedly re-evaluates

  2. Oct 19, 2026 · Maintainer security tabs

    Updated

    A denial of service (DoS) vulnerability was identified in when Server-Side Rendering (SSR) is enabled on Node.js (V8). During route recognition, fails to validate whether an auxiliary outlet segment in the URL matches a route configured for that specific outlet name. Because unconfigured empty-path outlet groups (such as , , or ) are not rejected during matching, the router repeatedly re-evaluates

Sources

  • Maintainer security tabsVendor advisoryGHSA-62vg-58rm-qff7

    A denial of service (DoS) vulnerability was identified in when Server-Side Rendering (SSR) is enabled on Node.js (V8). During route recognition, fails to validate whether an auxiliary outlet segment in the URL matches a route configured for that specific outlet name. Because unconfigured empty-path outlet groups (such as , , or ) are not rejected during matching, the router repeatedly re-evaluates

    github.com

Freshness

Last verified in this catalog Nov 3, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026