Advisoriesby IbisSeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control
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.goweed/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:...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| github.com/seaweedfs/seaweedfs Go | < 0.0.0-20260512171108-5e8f99f40a8a | 0.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
- github.com/seaweedfs/seaweedfs/security/advisories/GHSA-2v6v-25fm-p4fg
- nvd.nist.gov/vuln/detail/CVE-2026-72920
- github.com/seaweedfs/seaweedfs/pull/9442
- github.com/seaweedfs/seaweedfs/commit/5e8f99f40a8abc7b449aefd260516443377041c7
- github.com/seaweedfs/seaweedfs
- github.com/seaweedfs/seaweedfs/releases/tag/4.24
More seaweedfs advisories
All seaweedfs
SeaweedFS: Filer JWT allowed_prefixes literal prefix match allows cross-tenant access to sibling pathsCVE-2026-72921fixed in 0.0.0-20260512171048-05ed5c9ae8a2SeaweedFS: Path traversal in the S3 gateway X-Amz-Copy-Source header allows cross-bucket object readCVE-2026-55874fixed in 0.0.0-20260612000715-b44cf51fe931seaweedfs: improper authorizationCVE-2026-55873fixed in 0.0.0-20260614205536-b13463880c1fSeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket accessCVE-2026-54917fixed in 0.0.0-20260526080459-dd1b4287899eSeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedleCVE-2026-73080fixed in 0.0.0-20260512171120-69da20bdaec9SeaweedFS Vulnerable to SQL InjectionCVE-2024-40120fixed in 0.0.0-20240625155419-9ac102336200