CVE-2026-58372

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

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, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-40360 (ENISA EUVD) · GHSA-9cq9-w9qm-wc9p (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
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: 0.9%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

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.1HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.9%
EPSS %ILE
58th
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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, Track* at medium and Attend at high mission impact.

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 no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 30, 2026

Last Modified

October 8, 2026

Advisory Details (6)

Auto-updated Jun 30, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

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

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 pull request

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

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 / EcosystemFix (by version range) / 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 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 10× in last 7d / 51× 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 100 of 293 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. None are among the latest 100 rows. The 193 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-58372?
CVE-2026-58372 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-58372 was made public on June 15, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 30, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-58372 actively exploited?
CVE-2026-58372 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58372?
CVE-2026-58372 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58372?
A fix for CVE-2026-58372 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58372 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-58372

Explore →

Is Your Infrastructure Affected by CVE-2026-58372?

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