Skip to content- Sources: primary
- Summary: SeaweedFS 4.53, released on 2026-11-08, binds S3 Tables DeleteNamespace and vector bucket cleanup to the authorized records, requires the matching actions to change a bucket's CORS or versioning, makes S3 Tables policy conditions fail safe, and stops plugin workers from forwarding the admin stream token to job RPCs. It adds per-bucket Block Public Access (BlockPublicAcls and IgnorePublicAcls), rejects POST Object header fields with control characters, and checks a needle's CRC the first time a range of it is read. The notes list no CVE IDs.
- Why it matters: Clusters that expose the SeaweedFS S3 gateway to several identities should upgrade, because several of these fixes close authorization gaps between S3 actions.
- Background: SeaweedFS is a distributed object store with a filer layer and an S3-compatible gateway. S3 Block Public Access settings make a bucket refuse or ignore public ACLs regardless of what individual uploads request. S3 Tables and S3 Vectors are newer AWS APIs for Iceberg tables and vector indexes that SeaweedFS has been reimplementing.