CVE-2026-84394

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-70282 (ENISA EUVD) · GHSA-58mr-gqgx-xq4g (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.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

fast-uri accepts a host that contains an unbalanced or misplaced authority bracket without reporting an error. A host that starts with an opening bracket but does not end with a closing bracket is neither validated as an IP literal nor canonicalized as a domain name, so parse() returns it as the host with error undefined, while Node's URL and the HTTP clients built on it resolve the same string to a different host. An application that reads the parsed host to make a host decision, such as an SSRF denylist, a redirect allowlist, or proxy routing, and then passes the original URL to an HTTP client evaluates its policy against a string that is not the host the request reaches. The same host is carried through normalize, equal, and resolve. This affects fast-uri versions 2.4.5, 3.1.6, and 4.1.3, and is fixed in 2.4.6, 3.1.7, and 4.1.4, where parse() reports a malformed host for any host that contains a bracket but is not a valid IPv6 literal.

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.4% × 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.4%
EPSS %ILE
31st
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.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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: 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.

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

September 2, 2026

Last Modified

September 4, 2026

Advisory Details (2)

Auto-updated Sep 2, 2026
Patch available. Sources: github.
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
GitHub advisoryMentions a patch (unverified)

fast-uri vulnerable to host confusion via an unclosed bracket in the URI authority · Advisory · fastify/fast-uri · GitHub

https://github.com/fastify/fast-uri/security/advisories/GHSA-58mr-gqgx-xq4g

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17917882672026-10-19redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17908280122026-10-15redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17918656602026-10-13redhat
redhatrhdh/rhdh-hub-rhel9:17913114952026-10-08redhat
redhatsatellite/iop-remediations-rhel9:17913484392026-10-08redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17906099542026-10-07redhat
redhatquay/quay-rhel8:17908084432026-10-07redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:17912496402026-10-06redhat
redhatquay/quay-rhel9:17906902982026-10-01redhat
redhatcluster-observability-operator/troubleshooting-panel-console-plugin-rhel9:17908544942026-10-01redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17904836792026-10-01redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17904836082026-10-01redhat
redhatforeman-0:3.18.0.14-1.el9sat2026-10-01redhat
redhatansible-automation-platform-27/mcp-server-rhel9:17895189692026-09-23redhat
redhatansible-automation-platform-tech-preview/mcp-server-rhel9:17896690362026-09-23redhat
redhatnetwork-observability/network-observability-console-plugin-rhel9:17899782772026-09-23redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17895678492026-09-22redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17895176822026-09-22redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17895928062026-09-22redhat
redhatrhdh/rhdh-hub-rhel9:17895542852026-09-21redhat
redhatdiscovery/discovery-ui-rhel9:17896774592026-09-21redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17896131072026-09-17redhat
redhatsatellite/iop-advisor-frontend-rhel9:17896595732026-09-17redhat
redhatrhmtc/openshift-migration-ui-rhel8:17895463732026-09-17redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17896245192026-09-17redhat
redhatsatellite/iop-remediations-rhel9:17896155932026-09-17redhat
redhatsatellite/iop-advisor-frontend-rhel9:17896595652026-09-17redhat
redhatdevspaces/openvsx-rhel9:17891442692026-09-17redhat
redhatrhem/flightctl-ui-rhel10:17894881112026-09-16redhat
redhatrhem/flightctl-ui-ocp-rhel9:17894864462026-09-16redhat

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

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-ajv8.12.0~ds+~2.1.1-5 ... 8.20.0~ds+~cs7.1.6-1 (15 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-ajv8.12.0~ds+~2.1.1-5 ... 8.20.0~ds+~cs7.1.4-1 (13 versions)
  • every version up to 8.20.0~ds+~cs7.1.5-1: fixed in 8.20.0~ds+~cs7.1.5-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
fast-uri4.1.3
  • 2.4.5 up to 2.4.6: fixed in 2.4.6
  • 3.1.6 up to 3.1.7: fixed in 3.1.7
  • 4.1.3 up to 4.1.4: fixed in 4.1.4
—

Weakness Classification(1)

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

Additional Vendor Advisories

(20)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 77× 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 167 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 67 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-84394?
CVE-2026-84394 is a high-severity vulnerability; its CVE record was published on September 2, 2026. fast-uri accepts a host that contains an unbalanced or misplaced authority bracket without reporting an error. A host that starts with an opening bracket but does not end with a closing bracket is neither validated as an IP literal nor canonicalized as a domain name, so parse() returns it as the…
When was the CVE record for CVE-2026-84394 published?
The CVE record for CVE-2026-84394 was published on September 2, 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 September 4, 2026; the record at its source may have been updated since.
Is CVE-2026-84394 actively exploited?
CVE-2026-84394 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84394?
CVE-2026-84394 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-84394?
A fix for CVE-2026-84394 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-84394 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-84394

Explore →

Is Your Infrastructure Affected by CVE-2026-84394?

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