CVE-2026-47219

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

find-my-way is a framework-independent HTTP router that internally uses a Radix Tree and supports route parameters and wildcards. Versions prior to 9.7.0 are vulnerable to remotely triggerable DoS in find-my-way when it is used with Node's HTTP/2 server. The lookup() function passes req.method into find(), and find() indexes this.trees[method]. Since this.trees is a normal object, HTTP/2 method values like constructor, toString, or __proto__ can resolve inherited object properties instead of returning undefined. The code then treats that value like a router node and crashes when it reaches currentNode.prefix.length. This issue has been fixed in version 9.0.7.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 28, 2026
Patch available. Sources: github.
github Patch Available

DDoS with HTTP2 · Advisory · delvedor/find-my-way · GitHub

https://github.com/delvedor/find-my-way/security/advisories/GHSA-c96f-x56v-gq3h

Vendor Advisories for CVE-2026-47219(5)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmulticluster-engine/console-mce-rhel9:17866688562026-08-25redhat

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 rangeFixed inDependents
find-my-way—9.7.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 55× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-26 06:53 UTCVendor advisory
  2. 2026-08-25 17:45 UTCEG score recompute
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 15:49 UTCEG score recompute
  5. 2026-08-23 01:49 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 01:07 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 00:30 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 23:40 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 22:49 UTCEG score recompute
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 22:05 UTCEG score recompute
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 21:26 UTCEG score recompute
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 09:07 UTCEG score recompute
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 08:30 UTCEG score recompute
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 07:53 UTCEG score recompute
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-12 18:57 UTCEG score recompute
Show 32 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 18:19 UTCEG score recompute
  3. 2026-08-11 05:48 UTCEG score recompute
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-09 16:52 UTCEG score recompute
  6. 2026-08-09 13:46 UTCEPSS rescore
  7. 2026-08-09 04:34 UTCEG score recompute
  8. 2026-08-08 16:37 UTCEPSS rescore
  9. 2026-08-08 03:57 UTCEG score recompute
  10. 2026-08-06 15:01 UTCEG score recompute
  11. 2026-08-06 13:47 UTCEPSS rescore
  12. 2026-08-06 02:42 UTCEG score recompute
  13. 2026-08-05 19:17 UTCEPSS rescore
  14. 2026-08-05 00:59 UTCEG score recompute
  15. 2026-08-04 15:10 UTCEPSS rescore
  16. 2026-08-04 12:39 UTCEG score recompute
  17. 2026-08-04 10:39 UTCEPSS rescore
  18. 2026-08-03 11:00 UTCEG score recompute
  19. 2026-08-03 10:36 UTCEPSS rescore
  20. 2026-08-02 09:50 UTCEG score recompute
  21. 2026-08-02 02:27 UTCEPSS rescore
  22. 2026-08-01 09:13 UTCEG score recompute
  23. 2026-08-01 04:16 UTCEPSS rescore
  24. 2026-07-30 17:06 UTCEG score recompute
  25. 2026-07-30 16:28 UTCEPSS rescore
  26. 2026-07-30 04:44 UTCEG score recompute
  27. 2026-07-30 01:30 UTCEPSS rescore
  28. 2026-07-29 16:25 UTCEG score recompute
  29. 2026-07-29 15:34 UTCEG score recompute
  30. 2026-07-28 23:23 UTCEG score recompute
  31. 2026-07-26 22:04 UTCEG score recompute
  32. 2026-07-23 20:12 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47219?
CVE-2026-47219 is a high vulnerability published on July 23, 2026. find-my-way is a framework-independent HTTP router that internally uses a Radix Tree and supports route parameters and wildcards. Versions prior to 9.7.0 are vulnerable to remotely triggerable DoS in find-my-way when it is used with Node's HTTP/2 server. The lookup() function passes req.method into…
When was CVE-2026-47219 disclosed?
CVE-2026-47219 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47219 actively exploited?
CVE-2026-47219 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.3% of all scored CVEs.
What is the CVSS score of CVE-2026-47219?
CVE-2026-47219 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-47219?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47219, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-47219?

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

Start Free Scan →Browse All CVEs