Skip to content

← Actionable
Medium, CVSS 4.3amended

SeaweedFS: Improper authorization in the S3Tables / Iceberg REST management API lets a low-privileged S3 user enumerate administrator-owned table buckets

CVE-2026-55873GHSA-hgpf-8634-g44c

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-20260614205536-b13463880c1f), 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.

Affected packages

  • Go github.com/seaweedfs/seaweedfs

    Affected
    >= 0.0.0-20260128085517-09bb90e8dc16, < 0.0.0-20260614205536-b13463880c1f
    Fixed in
    0.0.0-20260614205536-b13463880c1f

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-55873: 0.34% estimated exploitation activity in the next 30 days; percentile 27.81 (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 SeaweedFS routes requests signed with SigV4 service s3tables to the S3Tables management API. Authorization on that path collapsed account-less S3 identities into the shared admin account and failed open, so a user holding only ordinary S3 Read credentials — and no S3Tables-specific permission — could invoke S3Tables management operations such as GET /buckets and enumerate administrator-owned table bucket inventory (names and ARNs). The same handler backs the Iceberg REST catalog, which was affected by the same flaw. Impact An authenticated low-privileged S3 user can cross the boundary between ordinary S3 object access and S3Tables management. Confirmed impact is disclosure of administrator-owned table bucket inventory (bucket names and ARNs); in shared or multi-tenant deployments this can reveal tenant naming and operational structure. Affected versions SeaweedFS = 4.08, < 4.34 (the S3Tables management API was introduced in 4.08). Patched versions Fixed in 4.34 (#9961).…

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

    Amended from ghsa record GHSA-hgpf-8634-g44c

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6329

  3. Revision 1 · created ·

    Published from osv record GHSA-hgpf-8634-g44c

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-55873

Advisory: SeaweedFS: Improper authorization in the S3Tables / Iceberg REST management API lets a low-privileged S3 user enumerate administrator-owned table buckets
IDs: CVE-2026-55873, GHSA-hgpf-8634-g44c
Record: https://patchnext.com/advisories/cve-2026-55873 (revision 3, 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: Medium (CVSS 4.3)
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-20260614205536-b13463880c1f. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/seaweedfs/seaweedfs: affected >= 0.0.0-20260128085517-09bb90e8dc16, < 0.0.0-20260614205536-b13463880c1f; fixed in 0.0.0-20260614205536-b13463880c1f

## 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-hgpf-8634-g44c (OSV record GHSA-hgpf-8634-g44c lists affected ranges: Go github.com/seaweedfs/seaweedfs >=0.0.0-20260128085517-09bb90e8dc16 <0.0.0-20260614205536-b13463880c1f (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6329 (OSV record GO-2026-6329 lists affected ranges: Go github.com/seaweedfs/seaweedfs >=0.0.0-20260128085517-09bb90e8dc16 <0.0.0-20260614205536-b13463880c1f (fixed))
- Verified: https://github.com/advisories/GHSA-hgpf-8634-g44c (GitHub-reviewed advisory GHSA-hgpf-8634-g44c lists affected ranges: Go github.com/seaweedfs/seaweedfs >=0.0.0-20260128085517-09bb90e8dc16 <0.0.0-20260614205536-b13463880c1f)

Commands are suggestions: review each one before running it.

Loading voting…