CVE-2026-111752

validatedZero produced an exploit or a check.

GHSA-62vg-58rm-qff7 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−20dkevAttacks confirmed in the real world.
npm:@angular/router >= 22.0.0, < 22.2.1; >= 21.0.0, < 21.2.25; >= 20.0.0, < 20.3.33; <= 19.2.25
fixed in 22.2.1, 21.2.25, 20.3.33
CWE-400 Uncontrolled Resource Consumption
ETK-2026-165, permanent identifier
pkg:npm/@angular/router
−20dTTV
36mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal +0dpublic poc+0dcheck available+0.2dagent stopped
0
+5d
+10d
+15d
+20d

description

Angular applications using @angular/router for on-demand Node.js server-side rendering may be affected when their routes include empty paths or named outlets. An unauthenticated attacker can send a malformed route URL that consumes worker memory or CPU, potentially terminating SSR processes; browser-only applications and build-time prerendering are not affected.

mitigation

Upgrade @angular/router to 22.2.1, 21.2.25, or 20.3.33, as appropriate for the maintained Angular release line. Until upgraded, reject auxiliary-outlet URL syntax at the edge or before the SSR handler, and apply a full request-target length limit; releases before 20 have no upstream patch.

fixed in 22.2.1, 21.2.25, 20.3.33

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−20d
Δ to kevAttacks confirmed in the real world.
–

outcome

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-30 19:32Z
  2. 2026-09-30 19:32Z

this entry in the feed

GET /api/v1/feed/CVE-2026-111752

{
  "etk_id": "ETK-2026-165",
  "cve_id": "CVE-2026-111752",
  "display_id": "CVE-2026-111752",
  "ghsa_id": "GHSA-62vg-58rm-qff7",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Route-matching denial of service in @angular/router",
  "summary": "Angular applications using @angular/router for on-demand Node.js server-side rendering may be affected when their routes include empty paths or named outlets. An unauthenticated attacker can send a malformed route URL that consumes worker memory or CPU, potentially terminating SSR processes; browser-only applications and build-time prerendering are not affected.",
  "mitigation": "Upgrade @angular/router to 22.2.1, 21.2.25, or 20.3.33, as appropriate for the maintained Angular release line. Until upgraded, reject auxiliary-outlet URL syntax at the edge or before the SSR handler, and apply a full request-target length limit; releases before 20 have no upstream patch.",
  "vendor": "npm",
  "product": "npm:@angular/router",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 22.0.0, < 22.2.1"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "22.2.1"
      ],
      "package_name": "@angular/router",
      "purl": "pkg:npm/@angular/router"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 21.0.0, < 21.2.25"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "21.2.25"
      ],
      "package_name": "@angular/router",
      "purl": "pkg:npm/@angular/router"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 20.0.0, < 20.3.33"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "20.3.33"
      ],
      "package_name": "@angular/router",
      "purl": "pkg:npm/@angular/router"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 19.2.25"
      ],
      "ecosystem": "npm",
      "fixed_versions": [],
      "package_name": "@angular/router",
      "purl": "pkg:npm/@angular/router"
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 35.69388285,
  "t0_at": null,
  "signals": {
    "check": {
      "at": "2026-09-30T23:36:54.547332+00:00",
      "days": -20.256963066539353,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T05:46:56.178670+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-09-30T19:32:57+00:00",
      "days": -20.426379123622684,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T05:46:56.178670+00:00",
      "url": "https://github.com/angular/angular/security/advisories/GHSA-62vg-58rm-qff7"
    },
    "trigger_signal": {
      "at": "2026-09-30T19:32:57+00:00",
      "days": -20.426379123622684,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T05:46:56.178670+00:00",
      "url": "https://github.com/angular/angular/security/advisories/GHSA-62vg-58rm-qff7"
    }
  }
}

published 2026-09-30 23:01Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.