CVE-2026-58372

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-30. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this weekElevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

SeaweedFS before 4.34 contains a path traversal vulnerability in the S3 gateway DeleteMultipleObjectsHandler that allows authenticated S3 principals with write access to a single bucket to delete arbitrary objects in other tenants' buckets by supplying object keys containing ../ sequences in the DeleteObjects XML request body. Attackers can bypass authorization controls through a confused deputy condition, as the validateRequestPath middleware only inspects URL-captured path variables and never examines request-body keys, allowing the filer path to collapse directory traversal sequences and resolve deletions outside the authorized bucket.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track*)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
65%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 14, 2026

Advisory Details (6)

Auto-updated Jun 30, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit, github_pr.
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
generic

SeaweedFS < 4.34 - Cross-Bucket Object Deletion via DeleteObjects Request-Body Keys | Advisories | VulnCheck

https://www.vulncheck.com/advisories/seaweedfs-cross-bucket-object-deletion-via-deleteobjects-request-body-keys
github_release Patch Available

4.34

Patch available: seaweedfs/seaweedfs 4.34

https://github.com/seaweedfs/seaweedfs/releases/tag/4.34
github_pr

[s3] validate indirect filer path inputs

Fix merged in seaweedfs/seaweedfs PR #9931 on 2026-06-12 — awaiting tagged release

https://github.com/seaweedfs/seaweedfs/pull/9931
github_commit

commit 0345658ea8e7 (seaweedfs/seaweedfs)

Fix landed in seaweedfs/seaweedfs commit 0345658ea8e7 — awaiting tagged release

https://github.com/seaweedfs/seaweedfs/commit/0345658ea8e7c6a3948ad190634b00866ec244c9
generic

oss/seaweedfs.md at main · geo-chen/oss · GitHub

https://github.com/geo-chen/oss/blob/main/seaweedfs.md

Vendor Advisories for CVE-2026-58372(2)

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 / EcosystemFixed in / PatchReleasedSource
redhatcryostat/cryostat-storage-rhel9:4.2.0-222026-09-16redhat

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 rangeFixed inDependents
github.com/seaweedfs/seaweedfs—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 / 51× 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 230 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-58372?
CVE-2026-58372 is a high vulnerability published on June 30, 2026. SeaweedFS before 4.34 contains a path traversal vulnerability in the S3 gateway DeleteMultipleObjectsHandler that allows authenticated S3 principals with write access to a single bucket to delete arbitrary objects in other tenants' buckets by supplying object keys containing ../ sequences in the…
When was CVE-2026-58372 disclosed?
CVE-2026-58372 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58372 actively exploited?
CVE-2026-58372 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 35.3% of all scored CVEs.
What is the CVSS score of CVE-2026-58372?
CVE-2026-58372 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-58372?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58372, 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-58372

Explore →

Is Your Infrastructure Affected by CVE-2026-58372?

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

Start Free Scan →Browse All CVEs