CVE-2026-6321

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 83% 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, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 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)
EPSS
40.7%
KEV
Not listed

Published

May 4, 2026

Last Modified

July 15, 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

Vendor Advisories for CVE-2026-6321(16)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatio.hawt-project2026-06-10redhat
redhatdevspaces/dashboard-rhel9:17806851762026-06-10redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17804671472026-06-10redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17800829492026-06-09redhat
redhatansible-automation-platform-tech-preview/mcp-server-rhel9:17797832482026-06-09redhat
redhatnetwork-observability/network-observability-console-plugin-rhel9:17805560692026-06-08redhat
redhatrhdh/rhdh-hub-rhel9:17798415862026-05-27redhat
redhatdiscovery/discovery-ui-rhel9:17793951882026-05-21redhat
redhatodf4/rook-ceph-rhel9-operator:17785776962026-05-19redhat

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 rangeFixed inDependents
fast-uri—3.1.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 45× 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 133 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 July 15, 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 40.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.

Start Free Scan →Browse All CVEs