Skip to content
seaweedfsGHSA-2v6v-25fm-p4fg

SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control

Critical9.8CVE-2026-72920 · Published Sep 2, 2026 · updated Sep 10, 2026

GitHub advisory

Affected versions

PackageAffectedFixed in
github.com/seaweedfs/seaweedfs
Go
< 0.0.0-20260512171108-5e8f99f40a8a0.0.0-20260512171108-5e8f99f40a8a
Details and references

### Impact The filer registered the IAM gRPC service (`SeaweedIdentityAccessManagement`) with no authentication. Any client able to reach the filer gRPC port could invoke IAM RPCs , `CreateUser`, `CreateAccessKey`, `PutUserPolicy`, and related calls , to mint credentials and grant itself S3 administrative privileges. This fully compromises the confidentiality, integrity, and availability of stored objects. No credentials are required, and enabling the documented JWT signing keys does not close it: the IAM gRPC service was not gated by that mechanism. Even under mTLS, the listener-level `allowed_commonNames` ACL applies to the port rather than to individual RPCs, so any cluster mesh certificate could reach these administrative calls. ### Affected component - `weed/server/filer_server_handlers_iam_grpc.go` - `weed/command/filer.go` ### Patches Fixed in **4.24**. Every IAM RPC now requires a Bearer token signed with the filer admin signing key (`jwt.filer_signing.key`), and the service refuses to register when no signing key is configured , removing the unauthenticated default entirely. ### Workarounds Restrict the filer gRPC port to trusted hosts. Configure `jwt.filer_signing.key` in `security.toml` and upgrade to 4.24; operators that use the IAM RPCs must attach an admin-signed Bearer token on each call. ### References - Fixed by seaweedfs/seaweedfs#9442 (follow-ups: #9498, #9508, #9514, #9536) - Reported by Kadir Arslan (https://github.com/KadirArslan)

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

More seaweedfs advisories

All
DateAdvisory
Sep 2SeaweedFS: Filer JWT allowed_prefixes literal prefix match allows cross-tenant access to sibling paths
CVE-2026-72921High8.1fixed in 0.0.0-20260512171048-05ed5c9ae8a2
Aug 28SeaweedFS: Path traversal in the S3 gateway X-Amz-Copy-Source header allows cross-bucket object read
CVE-2026-55874High7.7fixed in 0.0.0-20260612000715-b44cf51fe931
Aug 28SeaweedFS: Improper authorization in the S3Tables / Iceberg REST management API lets a low-privileged S3 user enumerate administrator-owned table buckets
CVE-2026-55873Medium4.3fixed in 0.0.0-20260614205536-b13463880c1f
Aug 12SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access
CVE-2026-54917Highfixed in 0.0.0-20260526080459-dd1b4287899e
Aug 11SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle
CVE-2026-73080Critical9.3fixed in 0.0.0-20260512171120-69da20bdaec9
May 162025SeaweedFS Vulnerable to SQL Injection
CVE-2024-40120Medium6.5fixed in 0.0.0-20240625155419-9ac102336200

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.