GHSA-2v6v-25fm-p4fg: Critical severity go/github.com/seaweedfs/seaweedfs vulnerability
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 allowedcommonNames ACL applies to the port rather than to individual RPCs, so any cluster mesh certificate could reach these administrative calls.
Affected component - weed/server/filerserverhandlersiamgrpc.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.filersigning.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.filersigning.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)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/seaweedfs/seaweedfsto a version that resolves this vulnerability.Fixed in 0.0.0-20260512171108-5e8f99f40a8a - Upgrade
Upgrade
seaweedfs/seaweedfsto a version that resolves this vulnerability.Fixed in 4.24 - Configuration
Configure jwt.filer_signing.key in security.toml so every IAM gRPC call requires a Bearer token signed with the filer admin signing key; operators using IAM RPCs must attach an admin-signed Bearer token on each call.
SeaweedFS jwt.filer_signing.key = <configure an admin signing key value in security.toml> - Configuration
Restrict the SeaweedFS filer gRPC port (including the IAM gRPC service SeaweedIdentityAccessManagement) to trusted hosts using the listener-level allowed_commonNames ACL.
filer gRPC listener allowed_commonNames (ACL) = restrict to trusted hosts via allowed_commonNames at the port/listener level - Compensating control
Ensure clients connecting to the filer gRPC port are limited to trusted hosts/cluster components, since allowed_commonNames applies to the whole port rather than individual RPCs (even under mTLS).
Event History
Frequently Asked Questions
Who can exploit this issue?
Any client that can reach the filer gRPC port can invoke the affected IAM RPCs. No credentials are required.
Does enabling JWT signing keys protect an affected deployment?
No. The IAM gRPC service was not gated by the documented JWT signing-key mechanism in affected versions.
Does mTLS prevent unauthorized IAM operations?
Not by itself. The listener-level allowed_commonNames ACL controls access to the port, so any client with a cluster mesh certificate permitted on that port could reach the administrative RPCs.
What can be done before upgrading?
Restrict access to the filer gRPC port to trusted hosts. The issue is fixed in version 4.24, where IAM RPCs require a Bearer token signed with jwt.filer_signing.key and the service will not register without that signing key.