CVE-2026-72920: SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control
SeaweedFS is a distributed storage system. Prior to 4.24, the filer registers the SeaweedIdentityAccessManagement gRPC service without mandatory authentication when jwt.filersigning.key is unset, allowing any client that can reach the filer gRPC port to invoke CreateUser, CreateAccessKey, PutPolicy, and related IAM RPCs to mint credentials and gain S3 administrative control. This issue is fixed in versions 4.24.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
SeaweedFS (filer)to a version that resolves this vulnerability.Fixed in 4.24
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72920?
The severity of CVE-2026-72920 is rated as critical with a score of 9.8.
What does CVE-2026-72920 affect?
CVE-2026-72920 affects the SeaweedFS distributed storage system, specifically its unauthenticated gRPC service.
How do I fix CVE-2026-72920?
To fix CVE-2026-72920, set the jwt.filer_signing.key to enforce authentication on the SeaweedIdentityAccessManagement gRPC service.
What are the risks of CVE-2026-72920?
CVE-2026-72920 allows unauthenticated clients to gain administrative control over S3 operations, posing significant security risks.
When was CVE-2026-72920 published?
CVE-2026-72920 was published on August 11, 2026.