# CVE-2026-54917: SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access

> Attackers can access or modify data in unauthorized buckets via path traversal in SeaweedFS S3 and Iceberg gateways.

- **Severity:** High 7.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** MINI-ffj2-828w-ffrj, MINI-q3mg-m32h-9cmh

## What is CVE-2026-54917?

CVE-2026-54917 is a high-severity path traversal vulnerability in seaweedfs, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

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

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

It affects 1 product.


Products: Seaweedfs Seaweedfs.

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

Upgrade to a fixed version.

## Is CVE-2026-54917 being exploited?

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

Public exploit code:

- PoC + analysis for CVE-2026-54917 — SeaweedFS S3 gateway cross-bucket path traversal (CVSS 10.0, <4.30). Read/write any bucket via .. in the object key. (github_poc): https://github.com/BiiTts/CVE-2026-54917-SeaweedFS-Cross-Bucket-Traversal
- SeaweedFS <= 4.29 - Path Traversal File Write (nuclei): http/cves/2026/CVE-2026-54917.yaml

## Other vulnerabilities in seaweedfs

- [CVE-2026-100413](https://insights.sbomify.com/CVE-2026-100413/): SeaweedFS: Hard-coded SSH host key can be presented by certain standalone SFTP Helm deployments (high 7.0)
- [CVE-2024-40120](https://insights.sbomify.com/CVE-2024-40120/): SeaweedFS Vulnerable to SQL Injection (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54917 is a high-severity path traversal vulnerability in seaweedfs, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54917 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-54917/ (Markdown: https://insights.sbomify.com/CVE-2026-54917/index.md)
```

## Sources

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

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