CVE-2026-6321

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%, top 58% 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: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

fast-uri decoded percent-encoded path separators and dot segments before applying dot-segment removal in its normalize() and equal() functions. Encoded path data was treated like real slashes and parent-directory references, so distinct URIs could collapse onto the same normalized path. Applications that normalize or compare attacker-controlled URLs to enforce path-based policy can be bypassed, with a path that appears confined under an allowed prefix normalizing to a different location. Versions <= 3.1.0 are affected. Update to 3.1.1 or later.

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%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

May 4, 2026

Last Modified

August 24, 2026

Advisory Details (2)

Auto-updated May 4, 2026
Patch available. Sources: github.
github Patch Available

fast-uri vulnerable to path traversal via percent-encoded dot segments · Advisory · fastify/fast-uri · GitHub

https://github.com/fastify/fast-uri/security/advisories/GHSA-q3j6-qgpj-74h6
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Patch Availability(21)

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-ajv6.12.6-3 ... 8.8.2~ds+~2.1.1-1 (17 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-ajv8.12.0~ds+~2.1.1-5 ... 8.20.0~ds+~cs7.1.3-1 (10 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-ajv8.12.0~ds+~2.1.1-5 ... 8.18.0~ds+~cs6.1.1-2 (7 versions)8.20.0~ds+~cs6.1.3-1
npm(1)
PackageVulnerable rangeFixed inDependents
fast-uri3.1.1

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 10× in last 7d / 79× 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 210 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-6321?
CVE-2026-6321 is a high vulnerability published on May 4, 2026. fast-uri decoded percent-encoded path separators and dot segments before applying dot-segment removal in its normalize() and equal() functions. Encoded path data was treated like real slashes and parent-directory references, so distinct URIs could collapse onto the same normalized path.…
When was CVE-2026-6321 disclosed?
CVE-2026-6321 was first published in the National Vulnerability Database on May 4, 2026, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6321 actively exploited?
CVE-2026-6321 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.4% of all scored CVEs.
What is the CVSS score of CVE-2026-6321?
CVE-2026-6321 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-6321?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6321, 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-6321

Explore →

Is Your Infrastructure Affected by CVE-2026-6321?

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