AI and data stack advisories

Severe, 6 weeks1496Projects326

1496 severe, 6 weeks · 326 projects

seaweedfsGHSA-hgpf-8634-g44c

seaweedfs: improper authorization

seaweedfs

CVE-2026-55873 · Published Aug 28, 2026 · updated Sep 2, 2026

Medium4.3
Fix: upgrade to 0.0.0-20260614205536-b13463880c1f or later
GitHub advisory

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

Affected versions

PackageAffectedFixed in
github.com/seaweedfs/seaweedfs
Go
>= 0.0.0-20260128085517-09bb90e8dc16, < 0.0.0-20260614205536-b13463880c1f0.0.0-20260614205536-b13463880c1f
Details and references

### 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**.

CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Severity from
GitHub (reviewed advisory)
Weakness
CWE-863
Also known as
BIT-seaweedfs-2026-55873, CVE-2026-55873, GO-2026-6329

More seaweedfs advisories

All seaweedfs