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…
Published Aug 28, 2026
Affected packages
github.com/seaweedfs/seaweedfs
- Ecosystem
- Go
- Affected
- >= 0.0.0-20260128085517-09bb90e8dc16, < 0.0.0-20260614205536-b13463880c1f
- Fixed in
- 0.0.0-20260614205536-b13463880c1f
- Check
go list -m github.com/seaweedfs/seaweedfs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to TA-MU-TA.
References
- https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-hgpf-8634-g44c
- https://nvd.nist.gov/vuln/detail/CVE-2026-55873
- https://github.com/seaweedfs/seaweedfs/pull/9961
- https://github.com/seaweedfs/seaweedfs/commit/b13463880c1fa62e255c058a9228b63cc95b4b36
- https://github.com/seaweedfs/seaweedfs/releases/tag/4.34
- https://github.com/advisories/GHSA-hgpf-8634-g44c
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-72920
SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control
critical9.8Sep 2, 2026CVE-2026-72921
SeaweedFS: Filer JWT allowed_prefixes literal prefix match allows cross-tenant access to sibling paths
high8.1Sep 2, 2026CVE-2026-55874
SeaweedFS: Path traversal in the S3 gateway X-Amz-Copy-Source header allows cross-bucket object read
high7.7Aug 28, 2026CVE-2026-54917
SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access
high7.8Aug 12, 2026CVE-2026-73080
SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle
critical9.3Aug 11, 2026CVE-2024-40120
SeaweedFS Vulnerable to SQL Injection
medium6.5May 16, 2025
