CVE-2026-54917

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 1.6% (76th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-39535 (ENISA EUVD) · GHSA-w62w-66v9-vvgv (GitHub Security Advisories) · GO-2026-6221 (OSV.dev)Source: ENISA EUVD

10.0EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.6%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

SeaweedFS is a distributed storage system for object storage (S3), file systems, and Iceberg tables. Prior to 4.30, the S3 API gateway and the Iceberg REST catalog gateway construct their routers with mux.NewRouter().SkipClean(true). With path cleaning disabled, a .. segment inside the URL survives routing, so a request such as GET /bucket-A/../evil-bucket/key, is matched as bucket=bucket-A, object=../evil-bucket/key. The captured object key is then joined into a filer path with util.JoinPath (S3) / path.Join (Iceberg), which collapse the .. server-side, so the actual read or write lands in evil-bucket. This vulnerability is fixed in 4.30.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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
1.6%
EPSS %ILE
76th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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 public PoC (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.

The score's inputs: 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

June 25, 2026

Last Modified

June 29, 2026

Advisory Details (2)

Auto-updated Nov 3, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access · Advisory · seaweedfs/seaweedfs · GitHub

https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-w62w-66v9-vvgv
GitHub pull request

s3,iceberg: reject `..` in URL path vars

Fix merged in seaweedfs/seaweedfs PR #9687 on 2026-05-26 — awaiting tagged release

https://github.com/seaweedfs/seaweedfs/pull/9687

Vendor Advisories for CVE-2026-54917(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/seaweedfs/seaweedfs @ 0.0.0-20260526080459-dd1b4287899e (fixes < 0.0.0-20260526080459-dd1b4287899e)—ghsa

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)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/seaweedfs/seaweedfs—
  • every version up to 0.0.0-20260526080459-dd1b4287899e: fixed in 0.0.0-20260526080459-dd1b4287899e
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 44× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 230 rows 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. None are among the latest 100 rows. The 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 08:21 UTCEchelonGraph re-scored
  2. 2026-11-13 08:21 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  4. 2026-11-12 07:14 UTCEchelonGraph re-scored
  5. 2026-11-12 07:13 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  7. 2026-11-11 06:02 UTCEchelonGraph re-scored
  8. 2026-11-11 06:02 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  9. 2026-11-10 16:44 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  10. 2026-11-10 04:55 UTCEchelonGraph re-scored
  11. 2026-11-10 04:55 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  12. 2026-11-09 16:35 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  13. 2026-11-09 03:48 UTCEchelonGraph re-scored
  14. 2026-11-09 03:48 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  15. 2026-11-08 16:40 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  16. 2026-11-08 02:41 UTCEchelonGraph re-scored
  17. 2026-11-08 02:41 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  18. 2026-11-07 16:39 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  19. 2026-11-07 01:34 UTCEchelonGraph re-scored
  20. 2026-11-07 01:34 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  21. 2026-11-06 16:38 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  22. 2026-11-06 12:25 UTCOSV refresh
  23. 2026-11-06 00:27 UTCEchelonGraph re-scored
  24. 2026-11-06 00:27 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  25. 2026-11-05 16:38 UTCEPSS rescoreEPSS 1.6% · 76th percentile
Show 75 more
  1. 2026-11-04 23:20 UTCEchelonGraph re-scored
  2. 2026-11-04 23:20 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  3. 2026-11-04 16:35 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  4. 2026-11-03 22:12 UTCEchelonGraph re-scored
  5. 2026-11-03 22:12 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  6. 2026-11-03 16:48 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  7. 2026-11-02 21:01 UTCEchelonGraph re-scored
  8. 2026-11-02 21:00 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  9. 2026-11-02 16:45 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  10. 2026-11-01 19:53 UTCEchelonGraph re-scored
  11. 2026-11-01 19:53 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  12. 2026-11-01 16:34 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  13. 2026-11-01 07:44 UTCGHSA enrichmentGHSA-w62w-66v9-vvgv · GitHub severity HIGH
  14. 2026-10-31 18:46 UTCEchelonGraph re-scored
  15. 2026-10-31 16:33 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  16. 2026-10-30 17:38 UTCEchelonGraph re-scored
  17. 2026-10-30 16:34 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  18. 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  19. 2026-10-29 16:32 UTCEchelonGraph re-scored
  20. 2026-10-28 16:32 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  21. 2026-10-28 15:24 UTCEchelonGraph re-scored
  22. 2026-10-27 16:32 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  23. 2026-10-27 14:17 UTCEchelonGraph re-scored
  24. 2026-10-26 16:31 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  25. 2026-10-26 12:43 UTCEchelonGraph re-scored
  26. 2026-10-25 16:33 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  27. 2026-10-25 14:19 UTCEchelonGraph re-scored
  28. 2026-10-25 11:32 UTCEchelonGraph re-scored
  29. 2026-10-24 16:33 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  30. 2026-10-24 10:23 UTCEchelonGraph re-scored
  31. 2026-10-23 16:32 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  32. 2026-10-23 09:16 UTCEchelonGraph re-scored
  33. 2026-10-22 16:34 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  34. 2026-10-22 08:09 UTCEchelonGraph re-scored
  35. 2026-10-21 16:33 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  36. 2026-10-21 07:00 UTCEchelonGraph re-scored
  37. 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  38. 2026-10-20 05:53 UTCEchelonGraph re-scored
  39. 2026-10-19 16:32 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  40. 2026-10-19 04:46 UTCEchelonGraph re-scored
  41. 2026-10-18 16:32 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  42. 2026-10-18 03:30 UTCEchelonGraph re-scored
  43. 2026-10-17 16:34 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  44. 2026-10-17 02:29 UTCEchelonGraph re-scored
  45. 2026-10-16 16:42 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  46. 2026-10-16 01:20 UTCEchelonGraph re-scored
  47. 2026-10-15 16:32 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  48. 2026-10-14 20:49 UTCEchelonGraph re-scored
  49. 2026-10-14 16:33 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  50. 2026-10-13 16:43 UTCEchelonGraph re-scored
  51. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  52. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  53. 2026-10-12 15:33 UTCEchelonGraph re-scored
  54. 2026-10-11 19:39 UTCEchelonGraph re-scored
  55. 2026-10-11 16:54 UTCEchelonGraph re-scored
  56. 2026-10-11 14:17 UTCEchelonGraph re-scored
  57. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  58. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  59. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  60. 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  61. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  62. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  63. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  64. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  65. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  66. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  67. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  68. 2026-09-29 15:22 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  69. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  70. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  71. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  72. 2026-09-24 14:04 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  73. 2026-09-23 17:54 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  74. 2026-09-23 08:30 UTCEchelonGraph re-scored
  75. 2026-09-20 20:16 UTCEPSS rescoreEPSS 1.2% · 67th percentile

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-54917.yaml
    Published Aug 24, 2026

    SeaweedFS <= 4.29 - Path Traversal File Write

    Open source ↗

Frequently asked(5)

What is CVE-2026-54917?
CVE-2026-54917 is a critical-severity vulnerability; its CVE record was published on June 25, 2026. SeaweedFS is a distributed storage system for object storage (S3), file systems, and Iceberg tables. Prior to 4.30, the S3 API gateway and the Iceberg REST catalog gateway construct their routers with mux.NewRouter().SkipClean(true). With path cleaning disabled, a .. segment inside the URL survives…
When was the CVE record for CVE-2026-54917 published?
The CVE record for CVE-2026-54917 was published on June 25, 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 June 29, 2026; the record at its source may have been updated since.
Is CVE-2026-54917 actively exploited?
CVE-2026-54917 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% probability of exploitation in the next 30 days (76th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54917?
CVE-2026-54917 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-54917?
A fix for CVE-2026-54917 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54917 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-54917

Explore →

Is Your Infrastructure Affected by CVE-2026-54917?

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