Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-54917: SeaweedFS is a distributed storage system for object storage (S3), file systems, and Iceberg tables

64
This week
CRITICAL 10.0REMOTEUPGRADE

CVE-2026-54917 is a critical-severity flaw (CVSS 10.0) affecting seaweedfs. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • Critical severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score10.0 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.6% (top 24%)
CISA exploited listNo
WeaknessCWE-22
Published2026-06-25
Last modified2026-06-29
Publisher (CNA): GitHub, Inc. · Vendor: seaweedfs

Share: LinkedIn · X · Reddit

Last updated 2026-06-29 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

seaweedfs seaweedfs UPGRADE
Affected: < 4.30
Fixed in: 4.30
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy seaweedfs || rpm -q seaweedfs || seaweedfs --version
2. UPGRADE to 4.30 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade seaweedfs
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade seaweedfs
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Exact fixes by distribution

Go · github.com/seaweedfs/seaweedfs · FIXED · 0.0.0-20260526080459-dd1b4287899e · vulnerable: < 0.0.0-20260526080459-dd1b4287899e · source
go get github.com/seaweedfs/seaweedfs@v0.0.0-20260526080459-dd1b4287899e go list -m github.com/seaweedfs/seaweedfs
Fedora 46 · python3.11 · FIXED · 3.11.18-1.fc46 · FEDORA-2026-cc775894f4 · source
sudo dnf upgrade --advisory=FEDORA-2026-cc775894f4

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-54917?

seaweedfs: upgrade to 4.30. Exact commands for each OS are on this page.

Is CVE-2026-54917 being exploited?

CVE-2026-54917 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-54917 affect?

CVE-2026-54917 affects seaweedfs. Severity is critical (CVSS 10.0). 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 p

How urgent is CVE-2026-54917?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.