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 — 3 sources updated 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(11)

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

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/console-rhel9:17873417802026-08-26redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatrhacm2/console-rhel9:17873392132026-08-26redhat
redhatrhacm2/console-rhel9:17873351052026-08-26redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatrhacm2/console-rhel9:17876870622026-08-26redhat
redhatmulticluster-engine/console-mce-rhel9:17866688562026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17872642502026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17870793592026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17872590482026-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 21× in last 7d / 72× 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.

Showing the most recent 100 of 119 total refreshes for this CVE.

  1. 2026-09-18 22:30 UTCEG score recompute
  2. 2026-09-18 22:30 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 03:03 UTCEG score recompute
  5. 2026-09-18 03:03 UTCVendor advisory
  6. 2026-09-17 02:01 UTCEG score recompute
  7. 2026-09-17 02:01 UTCVendor advisory
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 06:45 UTCEG score recompute
  10. 2026-09-16 06:45 UTCVendor advisory
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 09:52 UTCEG score recompute
  13. 2026-09-15 09:52 UTCVendor advisory
  14. 2026-09-14 06:40 UTCVendor advisory
  15. 2026-09-13 18:22 UTCEG score recompute
  16. 2026-09-13 18:22 UTCVendor advisory
  17. 2026-09-13 16:47 UTCEPSS rescore
  18. 2026-09-13 06:01 UTCVendor advisory
  19. 2026-09-12 17:42 UTCEG score recompute
  20. 2026-09-12 17:42 UTCVendor advisory
  21. 2026-09-12 15:01 UTCEPSS rescore
  22. 2026-09-12 05:07 UTCVendor advisory
  23. 2026-09-11 16:42 UTCEG score recompute
  24. 2026-09-11 16:42 UTCVendor advisory
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 03:25 UTCVendor advisory
  2. 2026-09-10 15:06 UTCEG score recompute
  3. 2026-09-10 15:06 UTCVendor advisory
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-09 08:53 UTCEG score recompute
  6. 2026-09-09 08:53 UTCVendor advisory
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 21:28 UTCEG score recompute
  9. 2026-09-07 21:28 UTCVendor advisory
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 08:29 UTCVendor advisory
  13. 2026-09-05 19:27 UTCEG score recompute
  14. 2026-09-05 19:27 UTCVendor advisory
  15. 2026-09-05 06:57 UTCEG score recompute
  16. 2026-09-05 06:57 UTCVendor advisory
  17. 2026-09-04 13:14 UTCEG score recompute
  18. 2026-09-04 13:14 UTCVendor advisory
  19. 2026-09-04 05:06 UTCEPSS rescore
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 23:21 UTCEG score recompute
  22. 2026-09-01 23:21 UTCVendor advisory
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-08-31 01:13 UTCEG score recompute
  25. 2026-08-31 01:13 UTCVendor advisory
  26. 2026-08-30 19:17 UTCEPSS rescore
  27. 2026-08-30 12:54 UTCEG score recompute
  28. 2026-08-30 12:54 UTCVendor advisory
  29. 2026-08-30 01:22 UTCEPSS rescore
  30. 2026-08-30 00:30 UTCEG score recompute
  31. 2026-08-30 00:30 UTCVendor advisory
  32. 2026-08-28 21:41 UTCEPSS rescore
  33. 2026-08-27 22:27 UTCVendor advisory
  34. 2026-08-27 10:09 UTCVendor advisory
  35. 2026-08-26 19:54 UTCEG score recompute
  36. 2026-08-26 19:54 UTCVendor advisory
  37. 2026-08-26 14:46 UTCEPSS rescore
  38. 2026-08-26 06:53 UTCVendor advisory
  39. 2026-08-25 17:45 UTCEG score recompute
  40. 2026-08-25 13:49 UTCEPSS rescore
  41. 2026-08-24 15:49 UTCEG score recompute
  42. 2026-08-23 01:49 UTCEG score recompute
  43. 2026-08-23 00:19 UTCEPSS rescore
  44. 2026-08-22 01:07 UTCEG score recompute
  45. 2026-08-21 23:49 UTCEPSS rescore
  46. 2026-08-21 00:30 UTCEG score recompute
  47. 2026-08-20 22:55 UTCEPSS rescore
  48. 2026-08-19 23:40 UTCEG score recompute
  49. 2026-08-19 17:04 UTCEPSS rescore
  50. 2026-08-18 22:49 UTCEG score recompute
  51. 2026-08-18 13:48 UTCEPSS rescore
  52. 2026-08-17 22:05 UTCEG score recompute
  53. 2026-08-17 13:47 UTCEPSS rescore
  54. 2026-08-16 21:26 UTCEG score recompute
  55. 2026-08-16 14:56 UTCEPSS rescore
  56. 2026-08-16 09:07 UTCEG score recompute
  57. 2026-08-16 02:14 UTCEPSS rescore
  58. 2026-08-15 08:30 UTCEG score recompute
  59. 2026-08-15 01:30 UTCEPSS rescore
  60. 2026-08-14 07:53 UTCEG score recompute
  61. 2026-08-13 22:00 UTCEPSS rescore
  62. 2026-08-12 18:57 UTCEG score recompute
  63. 2026-08-12 13:51 UTCEPSS rescore
  64. 2026-08-11 18:19 UTCEG score recompute
  65. 2026-08-11 05:48 UTCEG score recompute
  66. 2026-08-11 00:00 UTCEPSS rescore
  67. 2026-08-09 16:52 UTCEG score recompute
  68. 2026-08-09 13:46 UTCEPSS rescore
  69. 2026-08-09 04:34 UTCEG score recompute
  70. 2026-08-08 16:37 UTCEPSS rescore
  71. 2026-08-08 03:57 UTCEG score recompute
  72. 2026-08-06 15:01 UTCEG score recompute
  73. 2026-08-06 13:47 UTCEPSS rescore
  74. 2026-08-06 02:42 UTCEG score recompute
  75. 2026-08-05 19:17 UTCEPSS rescore

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 81.5% 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