CVE-2026-55873: SeaweedFS: Improper authorization in the S3Tables / Iceberg REST management API lets a low-privileged S3 user enumerate administrator-owned table buckets
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 ACTIONADMIN 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.
Other sources
SeaweedFS is a distributed storage system. In versions 4.08 through 4.33, requests signed with SigV4 service s3tables are routed to the S3Tables management API where authorization collapses account-less S3 identities into the shared admin account and fails open, allowing an authenticated low-privileged S3 user to enumerate administrator-owned table bucket names and ARNs. This issue is fixed in version 4.34.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/seaweedfs/seaweedfsto a version that resolves this vulnerability.Fixed in 0.0.0-20260614205536-b13463880c1f - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.34
Event History
Frequently Asked Questions
What is the severity of CVE-2026-55873?
CVE-2026-55873 has a medium severity rating of 4.3.
What vulnerability does CVE-2026-55873 address?
CVE-2026-55873 addresses improper authorization in the SeaweedFS S3Tables and Iceberg REST management API.
How does CVE-2026-55873 impact SeaweedFS users?
CVE-2026-55873 impacts SeaweedFS users by allowing low-privileged S3 users to enumerate administrator-owned table buckets.
What versions of SeaweedFS are affected by CVE-2026-55873?
SeaweedFS versions 4.08 through 4.33 are affected by CVE-2026-55873.
How can I mitigate the risks of CVE-2026-55873?
To mitigate the risks of CVE-2026-55873, users should upgrade to a version of SeaweedFS that addresses the vulnerability.