Is CVE-2026-58372 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-58372 being exploited in the wild.

How severe is CVE-2026-58372?

High severity, with a CVSS score of 8.1, published 30 June 2026.

Is there a fix for CVE-2026-58372?

A patch was published on 2026-06-11: Fix committed to master branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-58372 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-58372?

Check whether you run SeaweedFS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-58372: SeaweedFS path traversal in S3 gateway DeleteMultipleObjectsHandler

CVE-2026-58372 · Severity: high · CVSS 8.1 · Published 2026-06-30

SeaweedFS, a distributed storage system, contains a security flaw in its S3-compatible gateway. An authenticated user with permission to write to a single storage bucket can exploit this flaw to delete files in other users' or tenants' buckets. This could lead to unauthorized data loss and disruption of service across a shared storage environment.

Technologies: SeaweedFS. Vendors: SeaweedFS.

Quick answers

Is CVE-2026-58372 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-58372 being exploited in the wild.
How severe is CVE-2026-58372?: High severity, with a CVSS score of 8.1, published 30 June 2026.
Which products and versions are affected?: SeaweedFS < 4.34.
Is there a fix for CVE-2026-58372?: A patch was published on 2026-06-11: Fix committed to master branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-58372 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-58372?: Check whether you run SeaweedFS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A path traversal vulnerability exists in the SeaweedFS S3 gateway's DeleteMultipleObjectsHandler. The root cause is a 'confused deputy' condition where the validateRequestPath middleware only validates URL-captured path variables but fails to inspect object keys within the XML request body. An attacker can provide object keys containing '../' sequences which are subsequently collapsed by the filer path logic, resolving to locations outside the authorized bucket. This allows an authenticated user with limited bucket access to perform cross-tenant object deletion. The issue is fixed in version 4.34 by implementing stricter validation of indirect filer path inputs.

Affected products

SeaweedFS SeaweedFS < 4.34

Timeline

2026-06-11: patched: Fix committed to master branch
2026-06-30: disclosed: CVE published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.