Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.8amended

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

CVE-2026-54917GHSA-w62w-66v9-vvgv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/seaweedfs/seaweedfs 0.0.0-20260526080459-dd1b4287899e), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-54917: 1.64% estimated exploitation activity in the next 30 days; percentile 76.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
  • CVE-2026-58372: 0.87% estimated exploitation activity in the next 30 days; percentile 58.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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: 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. The captured path variables were never validated for traversal segments before reaching the handlers, so bucket isolation depended on downstream checks rather than on the path itself. Impact - With authentication disabled (enableAuth=false): direct cross-bucket read and write. An object key containing .. resolves to and operates on a different bucket than the one named in the request path. - With authentication enabled (enableAuth=true): an authorization confused-deputy. IAM evaluates the policy against the mux {bucket}…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-w62w-66v9-vvgv

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6221

  4. Revision 1 · created ·

    Published from osv record GHSA-w62w-66v9-vvgv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54917

Advisory: SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access
IDs: CVE-2026-54917, GHSA-w62w-66v9-vvgv
Record: https://patchnext.com/advisories/cve-2026-54917 (revision 4, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/seaweedfs/seaweedfs 0.0.0-20260526080459-dd1b4287899e. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/seaweedfs/seaweedfs: affected < 0.0.0-20260526080459-dd1b4287899e; fixed in 0.0.0-20260526080459-dd1b4287899e

## Suggested inspection (read-only)
- Go github.com/seaweedfs/seaweedfs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/seaweedfs/seaweedfs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-w62w-66v9-vvgv (OSV record GHSA-w62w-66v9-vvgv lists affected ranges: Go github.com/seaweedfs/seaweedfs >=0 <0.0.0-20260526080459-dd1b4287899e (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6221 (OSV record GO-2026-6221 lists affected ranges: Go github.com/seaweedfs/seaweedfs >=0 <0.0.0-20260526080459-dd1b4287899e (fixed))
- Verified: https://github.com/advisories/GHSA-w62w-66v9-vvgv (GitHub-reviewed advisory GHSA-w62w-66v9-vvgv lists affected ranges: Go github.com/seaweedfs/seaweedfs >=0 <0.0.0-20260526080459-dd1b4287899e)

Commands are suggestions: review each one before running it.

Loading voting…