Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.8
CVE-2026-72920: SeaweedFS: Unauthenticated access to S3 admin controls
CVE-2026-72920 · published 1 day ago
Summary
SeaweedFS, a distributed storage system, has a security issue that allows unauthorized users to gain full control over S3 settings. This could lead to data being deleted or modified without permission. To fix this, update to version 4.24 or later of SeaweedFS.
What to do
- Update seaweedfs to version 4.24.0.
- Update seaweedfs github.com/seaweedfs/seaweedfs to version 0.0.0-20260512171108-5e8f99f40a8a.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | seaweedfs | seaweedfs | < 4.24 |
| Bitnami | – | seaweedfs |
< 4.24.0 Fix: upgrade to 4.24.0
|
| Go | seaweedfs | github.com/seaweedfs/seaweedfs |
< 0.0.0-20260512171108-5e8f99f40a8a Fix: upgrade to 0.0.0-20260512171108-5e8f99f40a8a
|
Original advisory text
SeaweedFS: 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.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)
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)
References
- https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-2v6v-25fm-p4fg x_refsource_CONFIRM
- https://github.com/seaweedfs/seaweedfs/pull/9442 x_refsource_MISC
- https://github.com/seaweedfs/seaweedfs/commit/5e8f99f40a8abc7b449aefd26051644337... x_refsource_MISC
- https://github.com/seaweedfs/seaweedfs/releases/tag/4.24 x_refsource_MISC
- https://nvd.nist.gov/vuln/detail/CVE-2026-72920 URL
- https://github.com/seaweedfs/seaweedfs Product
Severity
9.8
Critical
CVSS 3.1: 9.8 (MITRE)
Exploitation
EPSS <1%
Type
CWE-306Missing Authentication for Critical Function
Timeline
Published2 Sep 2026
Updated2 Sep 2026
First seen11 Aug 2026
Sources
CVE-2026-72920 · NVD
CVE-2026-72920 · MITRE
BIT-seaweedfs-2026-72920 · OSV
GHSA-2v6v-25fm-p4fg · GHSA
GHSA-2v6v-25fm-p4fg · OSV
Monitor software like this
Free during beta