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.5% (37th percentile of EPSS-scored CVEs). 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.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 23, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 28, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

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(12)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatdevspaces/dashboard-rhel9:17891628842026-09-17redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatrhacm2/console-rhel9:17873392132026-08-26redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatrhacm2/console-rhel9:17873351052026-08-26redhat
redhatrhacm2/console-rhel9:17876870622026-08-26redhat
redhatrhacm2/console-rhel9:17873417802026-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 rangeFix by version rangeDependents
find-my-way—
  • every version up to 9.7.0: fixed in 9.7.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 56× 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 149 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Same product

2 shown

npm:find-my-way

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 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.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47219?
CVE-2026-47219 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47219?
A fix for CVE-2026-47219 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47219 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs