No access to your tenant or devices. Every item links to its source. What this means
SeaweedFS is a distributed storage system. Prior to 4.24, the filer registers the SeaweedIdentityAccessManagement gRPC service without mandatory authentication when jwt.filer_signing.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.
Read the publisher's advisorySeaweedFS is a distributed storage system. Prior to 4.24, the filer registers the SeaweedIdentityAccessManagement gRPC service without mandatory authentication when jwt.filer_signing.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.
Read the publisher's advisorySeaweedFS is a distributed storage system. Prior to 4.24, the filer registers the SeaweedIdentityAccessManagement gRPC service without mandatory authentication when jwt.filer_signing.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.
Read the publisher's advisory### 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)
Read the publisher's advisorySeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control in github.com/seaweedfs/seaweedfs
Read the publisher's advisoryVendor product
Shown as published. These rules are not interpreted as NuGet package version ranges.
{
"vendor": "seaweedfs",
"product": "seaweedfs",
"versions": [
{
"version": "< 4.24",
"status": "affected"
}
]
}Original source record · Cite this exact observation · Complete original publisher JSON
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
datePublished: Aug 11, 2026, 2:23:22 PM
dateUpdated: Aug 11, 2026, 2:46:46 PM
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-306
published: 2026-08-11T15:17:38.053
lastModified: 2026-09-09T20:46:02.457
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON
Go
SEMVER · introduced 0 → fixed 0.0.0-20260512171108-5e8f99f40a8a
Original source record · Cite this exact observation · Complete original publisher JSON
Go
SEMVER · introduced 0 → fixed 0.0.0-20260512171108-5e8f99f40a8a
Original source record · Cite this exact observation · Complete original publisher JSON