CVE-2026-72920 json
SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control
published 3mo ago modified 2mo ago also BIT-seaweedfs-2026-72920 , EUVD-2026-56156 , GHSA-2v6v-25fm-p4fg , GO-2026-6351
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/seaweedfs/seaweedfs 0.0.0-20260512171108-5e8f99f40a8a
- bitnami seaweedfs 4.24.0
- seaweedfs seaweedfs 4.24
- govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260916T180043-160000.1.1
suse advisories SUSE-SU-2026:23855-1SUSE-SU-2026:23863-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260916T180043-160000.1.1
opensuse advisories openSUSE-SU-2026:21897-1
Is CVE-2026-72920 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/seaweedfs/seaweedfs | <0.0.0-20260512171108-5e8f99f40a8a |
0.0.0-20260512171108-5e8f99f40a8a |
| bitnami | seaweedfs | <4.24.0 |
4.24.0 |
Affected products
- seaweedfs seaweedfs
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
github.com
/seaweedfs/seaweedfs/pull/9442
web, patch
-
github.com
/seaweedfs/seaweedfs/commit/5e8f99f40a8abc7b449aefd260516443377041c7
web, patch
-
github.com
/seaweedfs/seaweedfs/security/advisories/GHSA-2v6v-25fm-p4fg
web, advisory
-
github.com
/seaweedfs/seaweedfs/releases/tag/4.24
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-72920
advisory, web
-
github.com
/seaweedfs/seaweedfs
package
Sources
- CVE List CVE-2026-72920
- GitHub Advisory GHSA-2v6v-25fm-p4fg
- NVD CVE-2026-72920
- OSV BIT-seaweedfs-2026-72920
- OSV GO-2026-6351
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.