CVE-2026-75931

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.2%, top 86% 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.

fast-uri is a URI parser for Node.js. It canonicalizes a host to its ASCII form only when the input carries an explicit scheme, so a scheme-relative reference such as a host preceded by two slashes is returned with its host verbatim and no error set. As a result fast-uri's own entry points disagree with each other: parse, resolve, normalize, and equal can yield different hosts for the same input depending only on whether a scheme is written out, and equal can return opposite verdicts for the same pair of hosts. An application that extracts a host with fast-uri to check it against a policy list and then resolves the same reference can make its decision on one host while the destination is another, enabling host confusion and policy bypass. The affected versions are 2.4.2 up to but not including 2.4.5, 3.1.3 up to but not including 3.1.6, and 4.0.1 up to but not including 4.1.3. The issue is fixed in 2.4.5, 3.1.6, and 4.1.3, which canonicalize the host consistently across the resolve path. Users should upgrade to a patched version.

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
14%
KEV
Not listed

Published

August 24, 2026

Last Modified

September 2, 2026

Advisory Details (2)

Auto-updated Aug 24, 2026
Patch available. Sources: github.
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
github Patch Available

fast-uri vulnerable to host confusion via skipped IDN canonicalization on scheme-relative references · Advisory · fastify/fast-uri · GitHub

https://github.com/fastify/fast-uri/security/advisories/GHSA-5jgf-p345-68v8

Vendor Advisories for CVE-2026-75931(7)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatansible-automation-platform/automation-portal:17887757482026-09-08redhat
redhatansible-automation-platform/automation-portal:17887835912026-09-08redhat
redhatdiscovery/discovery-ui-rhel9:17882061962026-08-31redhat
redhatgrafana13-1-main-13.1.3-0.3.hum12026-08-29redhat
redhatgrafana13-2-main-13.2.0-0.1.2.hum12026-08-29redhat
redhatgrafana12-4-main-12.4.9-0.4.hum12026-08-29redhat

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 rangeFixed inDependents
node-ajv8.12.0~ds+~2.1.1-5 ... 8.20.0~ds+~cs7.1.5-1 (14 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-ajv8.12.0~ds+~2.1.1-5 ... 8.20.0~ds+~cs7.1.3-3 (12 versions)8.20.0~ds+~cs7.1.4-1—
npm(1)
PackageVulnerable rangeFixed inDependents
fast-uri—4.1.3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 92× 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-09-19 00:35 UTCEG score recompute
  2. 2026-09-19 00:35 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 13:19 UTCVendor advisory
  5. 2026-09-18 02:03 UTCEG score recompute
  6. 2026-09-18 02:03 UTCVendor advisory
  7. 2026-09-17 14:46 UTCVendor advisory
  8. 2026-09-17 03:28 UTCVendor advisory
  9. 2026-09-16 16:12 UTCEG score recompute
  10. 2026-09-16 16:12 UTCVendor advisory
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-16 04:55 UTCVendor advisory
  14. 2026-09-15 17:38 UTCVendor advisory
  15. 2026-09-15 06:22 UTCEG score recompute
  16. 2026-09-15 06:22 UTCVendor advisory
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-14 19:04 UTCVendor advisory
  19. 2026-09-14 07:47 UTCVendor advisory
  20. 2026-09-13 20:30 UTCEG score recompute
  21. 2026-09-13 20:30 UTCVendor advisory
  22. 2026-09-13 09:13 UTCVendor advisory
  23. 2026-09-12 21:57 UTCEG score recompute
  24. 2026-09-12 21:57 UTCVendor advisory
  25. 2026-09-12 15:02 UTCEPSS rescore
Show 67 more
  1. 2026-09-12 10:41 UTCVendor advisory
  2. 2026-09-11 23:24 UTCEG score recompute
  3. 2026-09-11 23:24 UTCVendor advisory
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 12:03 UTCEG score recompute
  6. 2026-09-11 12:03 UTCVendor advisory
  7. 2026-09-11 00:15 UTCVendor advisory
  8. 2026-09-10 12:10 UTCEG score recompute
  9. 2026-09-10 12:10 UTCVendor advisory
  10. 2026-09-10 09:35 UTCEPSS rescore
  11. 2026-09-10 00:37 UTCVendor advisory
  12. 2026-09-09 12:54 UTCVendor advisory
  13. 2026-09-09 01:34 UTCEG score recompute
  14. 2026-09-09 01:34 UTCVendor advisory
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-08 06:56 UTCVendor advisory
  17. 2026-09-07 19:31 UTCEG score recompute
  18. 2026-09-07 19:31 UTCVendor advisory
  19. 2026-09-07 08:14 UTCVendor advisory
  20. 2026-09-06 20:58 UTCEG score recompute
  21. 2026-09-06 20:58 UTCVendor advisory
  22. 2026-09-06 13:48 UTCEPSS rescore
  23. 2026-09-06 09:41 UTCVendor advisory
  24. 2026-09-05 22:25 UTCEG score recompute
  25. 2026-09-05 22:25 UTCVendor advisory
  26. 2026-09-05 11:07 UTCVendor advisory
  27. 2026-09-04 23:45 UTCEG score recompute
  28. 2026-09-04 23:45 UTCVendor advisory
  29. 2026-09-04 12:12 UTCEG score recompute
  30. 2026-09-04 12:12 UTCVendor advisory
  31. 2026-09-04 05:07 UTCEPSS rescore
  32. 2026-09-04 00:55 UTCVendor advisory
  33. 2026-09-03 13:38 UTCVendor advisory
  34. 2026-09-03 02:20 UTCVendor advisory
  35. 2026-09-02 15:01 UTCEG score recompute
  36. 2026-09-02 15:01 UTCVendor advisory
  37. 2026-09-02 14:12 UTCEPSS rescore
  38. 2026-09-02 03:46 UTCVendor advisory
  39. 2026-09-01 16:29 UTCEG score recompute
  40. 2026-09-01 16:29 UTCVendor advisory
  41. 2026-09-01 13:54 UTCEPSS rescore
  42. 2026-09-01 05:08 UTCEG score recompute
  43. 2026-09-01 05:08 UTCVendor advisory
  44. 2026-09-01 04:40 UTCEPSS rescore
  45. 2026-09-01 04:40 UTCEPSS rescore
  46. 2026-08-31 17:51 UTCVendor advisory
  47. 2026-08-31 04:32 UTCEG score recompute
  48. 2026-08-31 04:32 UTCVendor advisory
  49. 2026-08-30 19:18 UTCEPSS rescore
  50. 2026-08-30 19:17 UTCEPSS rescore
  51. 2026-08-30 17:15 UTCVendor advisory
  52. 2026-08-30 05:59 UTCEG score recompute
  53. 2026-08-30 01:22 UTCEPSS rescore
  54. 2026-08-29 07:20 UTCEG score recompute
  55. 2026-08-28 21:42 UTCEPSS rescore
  56. 2026-08-28 00:24 UTCEG score recompute
  57. 2026-08-27 14:25 UTCEPSS rescore
  58. 2026-08-27 01:43 UTCEG score recompute
  59. 2026-08-26 14:47 UTCEPSS rescore
  60. 2026-08-25 15:52 UTCEG score recompute
  61. 2026-08-25 13:49 UTCEPSS rescore
  62. 2026-08-24 17:19 UTCEG score recompute
  63. 2026-08-24 16:35 UTCEG score recompute
  64. 2026-08-24 14:18 UTCEPSS rescore
  65. 2026-08-24 10:24 UTCEG score recompute
  66. 2026-08-24 09:43 UTCEG score recompute
  67. 2026-08-24 09:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75931?
CVE-2026-75931 is a high vulnerability published on August 24, 2026. fast-uri is a URI parser for Node.js. It canonicalizes a host to its ASCII form only when the input carries an explicit scheme, so a scheme-relative reference such as a host preceded by two slashes is returned with its host verbatim and no error set. As a result fast-uri's own entry points disagree…
When was CVE-2026-75931 disclosed?
CVE-2026-75931 was first published in the National Vulnerability Database on August 24, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75931 actively exploited?
CVE-2026-75931 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 85.6% of all scored CVEs.
What is the CVSS score of CVE-2026-75931?
CVE-2026-75931 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-75931?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75931, 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-75931

Explore →

Is Your Infrastructure Affected by CVE-2026-75931?

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

Start Free Scan →Browse All CVEs