Skip to content

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

Moderate severity GitHub Reviewed Published Jun 26, 2026 in seaweedfs/seaweedfs

Package

gomod github.com/seaweedfs/seaweedfs (Go)

Affected versions

>= 0.0.0-20260128085517-09bb90e8dc16, < 0.0.0-20260614205536-b13463880c1f

Patched versions

0.0.0-20260614205536-b13463880c1f

Description

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). Administrator status is now decided by the
ACTION_ADMIN capability rather than by a collapsed admin account id, S3Tables
authorization no longer defaults to allow, and the tautological ListTableBuckets
gate was removed. Related hardening of the same root cause landed in #9962,
#9963, and #9971.

Workaround

No configuration workaround — upgrade to 4.34 or later.

Credit

Reported by TA-MU-TA.

References

@chrislusf chrislusf published to seaweedfs/seaweedfs Jun 26, 2026
Published by the National Vulnerability Database Jul 8, 2026
Published to the GitHub Advisory Database Aug 28, 2026
Reviewed Aug 28, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(27th percentile)

Weaknesses

Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. Learn more on MITRE.

CVE ID

CVE-2026-55873

GHSA ID

GHSA-hgpf-8634-g44c

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.