# CVE-2026-58372: SeaweedFS < 4.34 - Cross-Bucket Object Deletion via DeleteObjects Request-Body Keys

> Authenticated users can delete arbitrary objects in other tenants' buckets via path traversal in S3 DeleteObjects requests.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-9cq9-w9qm-wc9p

## What is CVE-2026-58372?

CVE-2026-58372 is a high-severity path traversal vulnerability in seaweedfs, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-58372?


## How do I fix CVE-2026-58372?

Upgrade to a fixed version.

## Is CVE-2026-58372 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58372 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58372 and fix it if it is affected.

What it is: CVE-2026-58372 is a high-severity path traversal vulnerability in seaweedfs, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58372 exists.

Affected product: seaweedfs. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-58372/ (Markdown: https://insights.sbomify.com/CVE-2026-58372/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58372
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58372
- OSV: https://osv.dev/vulnerability/CVE-2026-58372

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-58372/
Summaries are generated and may contain mistakes; the official description above is the record.