CVE-2026-6321

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.8% (54th 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
Trending — 3 sources updated this week
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.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.8% × 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.8%
EPSS %ILE
54th
KEV
Not listed

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

May 4, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated May 4, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

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
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

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

Vendor Advisories for CVE-2026-6321(20)

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

Patch Availability(22)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17902609542026-09-30redhat
redhatodf4/rook-ceph-rhel9-operator:17870615542026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17866295482026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatodf4/rook-ceph-rhel9-operator:17867031432026-08-18redhat
redhatautomation-gateway-0:2.5.20260715-1.el9ap2026-07-20redhat
redhatautomation-platform-ui-0:2.6.11-1.el9ap2026-07-20redhat
redhatrh-podman-desktop-0:1.1.1-1.el10_22026-07-09redhat
redhatcluster-observability-operator/troubleshooting-panel-console-plugin-rhel9:17828394942026-07-01redhat
redhatodf4/rook-ceph-rhel9-operator:17815574962026-06-16redhat
redhatrhdh/rhdh-hub-rhel9:17811873422026-06-16redhat
redhatodf4/rook-ceph-rhel9-operator:17811844682026-06-16redhat
redhatsatellite/iop-advisor-frontend-rhel9:17811816732026-06-16redhat
redhatdiscovery/discovery-ui-rhel9:17793951882026-06-15redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17804671472026-06-10redhat
redhatio.hawt-project2026-06-10redhat
redhatdevspaces/dashboard-rhel9:17806851762026-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
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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-ajv6.12.6-3 ... 8.8.2~ds+~2.1.1-1 (22 versions)
  • every version on: no fix on record
—
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.18.0~ds+~cs6.1.1-2 (7 versions)
  • every version up to 8.20.0~ds+~cs6.1.3-1: fixed in 8.20.0~ds+~cs6.1.3-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
fast-uri—
  • 3.0.0 up to 3.1.1: fixed in 3.1.1
  • every version up to 2.4.1: fixed in 2.4.1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 13× in last 7d / 30× 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 98 of 266 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 168 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-6321?
CVE-2026-6321 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-6321 published?
The CVE record for CVE-2026-6321 was published on May 4, 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 10, 2026; the record at its source may have been updated since.
Is CVE-2026-6321 actively exploited?
CVE-2026-6321 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6321?
CVE-2026-6321 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-6321?
A fix for CVE-2026-6321 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-6321 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-6321

Explore →

Is Your Infrastructure Affected by CVE-2026-6321?

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

Book a Demo →Browse All CVEs