CVE-2026-47219

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-23. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-50084 (ENISA EUVD) · GHSA-c96f-x56v-gq3h (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • 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/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 23, 2026

Last Modified

October 23, 2026

Advisory Details (1)

Auto-updated Jul 28, 2026
Patch available. Sources: github.
GitHub advisoryMentions 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

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-mod-arch-model-registry-rhel9:17918534322026-10-21redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17918609182026-10-19redhat
redhatdevspaces/dashboard-rhel9:17891628842026-09-17redhat
redhatrhacm2/console-rhel9:17873417802026-08-26redhat
redhatrhacm2/console-rhel9:17873351052026-08-26redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatrhacm2/console-rhel9:17876870622026-08-26redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatrhacm2/console-rhel9:17873392132026-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
npmfind-my-way @ 9.7.0 (fixes <= 9.6.0)—ghsa

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

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

Data Freshness Timeline

(refreshed 11× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 186 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 86 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-47219?
CVE-2026-47219 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-47219 published?
The CVE record for CVE-2026-47219 was published on July 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
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 (39th 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.