CVE-2026-75899

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 87% 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 decodes percent escapes in a hostname during parsing and then decodes the parsed hostname a second time during authority recomposition, so a single call to normalize or resolve can turn nested percent-encoded input into a different network destination such as a loopback hostname or address. For example, a doubly encoded host that spells out a loopback name decodes to that live host in one operation, which contradicts RFC 3986 section 2.4 that an implementation must not decode the same string more than once. An application that normalizes or resolves an untrusted HTTP-family URI before outbound routing, redirect validation, or a host-policy check can receive a destination different from the one the original encoded host represented, giving a server-side request forgery and host-policy bypass primitive. This is an incomplete-fix variant of CVE-2026-6322. The affected versions are 2.4.1 up to but not including 2.4.5, 3.1.2 up to but not including 3.1.6, and 4.0.0 up to but not including 4.1.3. The issue is fixed in 2.4.5, 3.1.6, and 4.1.3, which normalize percent escapes once and preserve encoded percent signs. 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
13%
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 server-side request forgery via repeated hostname percent-decoding · Advisory · fastify/fast-uri · GitHub

https://github.com/fastify/fast-uri/security/advisories/GHSA-fph4-wmhf-6fwf

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-uri4.1.3

Weakness Classification(2)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-75899?
CVE-2026-75899 is a high vulnerability published on August 24, 2026. fast-uri is a URI parser for Node.js. It decodes percent escapes in a hostname during parsing and then decodes the parsed hostname a second time during authority recomposition, so a single call to normalize or resolve can turn nested percent-encoded input into a different network destination such…
When was CVE-2026-75899 disclosed?
CVE-2026-75899 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-75899 actively exploited?
CVE-2026-75899 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 87.2% of all scored CVEs.
What is the CVSS score of CVE-2026-75899?
CVE-2026-75899 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-75899?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75899, 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-75899

Explore →

Is Your Infrastructure Affected by CVE-2026-75899?

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