CVE-2026-54917

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% 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
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 10.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.0(medium)
EPSS
26.6%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 29, 2026

Advisory Details (2)

Auto-updated Jul 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github.
github Patch Available🟡 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_pr

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54917?
CVE-2026-54917 is a critical vulnerability 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 CVE-2026-54917 disclosed?
CVE-2026-54917 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54917 actively exploited?
CVE-2026-54917 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54917, 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs