dbcve.org
SeaweedfsApplication

CVE-2026-54917

CRITICAL · 10.0 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to 4.30 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SeaweedFS prior to 4.30 has a path traversal vulnerability where the S3 API and Iceberg REST catalog gateways use mux.NewRouter().SkipClean(true), disabling URL path cleaning. This allows `..` sequences in URLs like `/bucket-A/../evil-bucket/key` to survive routing, and server-side path joining functions collapse the `..`, enabling unauthorized access to arbitrary buckets.

MitigationUpgrade SeaweedFS to version 4.30 or later, which enables path cleaning in the router configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SeaweedfsApplication
Affected:< 4.30

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SeaweedFS version
    Run 'weed version' or check the binary/version file that came with your installation
    Affected if version is below 4.30 and S3 or Iceberg gateway is in use
  2. Confirm S3 API gateway is enabled
    Check if port 8333 or 8334 is listening, or inspect configuration for s3.gateway section
    Affected if S3 gateway is exposed and SeaweedFS version is below 4.30
  3. Confirm Iceberg REST catalog is enabled
    Inspect configuration for iceberg.gateway or check if port 8088 is responding to Iceberg REST API requests
    Affected if Iceberg REST catalog is enabled and SeaweedFS version is below 4.30
  4. Review router configuration for SkipClean
    If you have access to source code or configuration, check if SkipClean(true) is set on HTTP routers used by S3 or Iceberg gateways
    Affected if SkipClean is explicitly set to true on S3 or Iceberg HTTP routers

You are affected if you run SeaweedFS version below 4.30 with either the S3 API gateway or Iceberg REST catalog gateway enabled, and requests can reach these services from clients or you host multi-tenant bucket access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.30 or later
Fixed in 4.30
Vendor patch github.com →
Interim mitigation

Upgrade SeaweedFS to version 4.30 or later, which enables path cleaning in the router configuration.

Recommended fix High confidence

4.30

  1. Backup your current SeaweedFS data and configuration files
  2. Stop the running SeaweedFS instance
  3. Download SeaweedFS version 4.30 or later from the official GitHub releases (https://github.com/seaweedfs/seaweedfs/releases)
  4. Replace the existing SeaweedFS binary with the new version
  5. Restart the SeaweedFS service
  6. Verify that the S3 API gateway and Iceberg REST catalog gateway are functioning correctly
  7. Test that path traversal attempts like /bucket-A/../evil-bucket/key are properly rejected
Caveat Review the release notes for 4.30 to check for any breaking changes related to S3 API or Iceberg functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Seaweedfs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54917 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54917 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data