Servers and applications
CVE-2026-72920
Unauthenticated filer IAM gRPC service grants S3 administrative control
- Severity
- Critical 9.8
- Published
- 8 Jul 2026
- Last changed
- 11 Aug 2026
- Added to UpHeron
- 22 Oct 2026
- Fixed in
- 4.24
- Exploit chance
- 0.8% in the next 30 daysHigher than 56% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Missing authentication (CWE-306)
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- Also known as
- GHSA-2v6v-25fm-p4fg
- Sources
- Project advisories (GitHub)
Description
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.
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.
Affected software
| Software | Affected versions |
|---|---|
SeaweedFSServers and applications · github:seaweedfs/seaweedfs |
|
About SeaweedFS
Fast distributed storage system for blobs, objects, files, and data lake, for billions of files. Blob store has O(1) disk seek, cloud tiering
- Docker Hub pulls
- 42,221,853Docker Hub, 15 Nov 2026
- GitHub stars
- 36,070GitHub, 15 Nov 2026
- Forks
- 3,114GitHub, 15 Nov 2026
- Latest release
- 4.53GitHub, 15 Nov 2026
- Released
- 8 Nov 2026GitHub
- License
- Apache Software License 2.0Wikidata
- Written in
- GoWikidata
- First released
- 21 Apr 2015Wikidata
- First published on GitHub
- 14 Jul 2014GitHub
Website Source code Docker image
Vulnerabilities in SeaweedFS
- In our list
- 58
- Published in the last 12 months
- 58
- Critical, last 12 months
- 17
- High, last 12 months
- 26
- Known exploited
- 0
- CVE-2026-129851SeaweedFS before 4.42 SSRF via VolumeServer.FetchAndWriteNeedle Replica URLsMedium 6.9 16 Nov 2026
- CVE-2026-129852SeaweedFS before 4.42 File Existence Disclosure via VolumeServer.FetchAndWriteNeedleMedium 6.9 16 Nov 2026
- GHSA-g96f-g546-47xfS3 gateway gRPC port exposes the IAM and lifecycle admin services without authentication when no filer signing key is configured, allowing anyone with network access to add an admin identityHigh 9 Nov 2026
- GHSA-5vhw-52xr-8x4jSTS AssumeRoleWithWebIdentity ignores trust policies when policy.defaultEffect is AllowMedium 9 Nov 2026
- GHSA-8rrx-349w-6396S3: object-scoped Write grant can change bucket configuration via the prefix query parameterMedium 9 Nov 2026
- GHSA-54j8-2gxc-wr9hS3 gateway applies response header overrides (response-content-type, response-content-disposition) to anonymous requests, enabling stored XSS on publicly readable bucketsMedium 6.1 9 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-72920
- GitHub Advisory Database https://github.com/advisories/GHSA-2v6v-25fm-p4fg
- github.com https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-2v6v-25fm-p4fg