Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
SeaweedFS versions up to but not including 0.0.0-20260512171108-5e8f99f40a8a expose an unauthenticated IAM gRPC service on the filer. Anyone who can reach the filer gRPC port can create users and access keys and grant themselves S3 administrative control over stored objects, with no credentials needed. Upgrade to 0.0.0-20260512171108-5e8f99f40a8a or later, which requires an admin-signed Bearer token for IAM calls. Until then, restrict the filer gRPC port to trusted hosts.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.8 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0078, the 56th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:13 UTC First seen by agentprime
- 31 Oct 2026, 14:13 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-2v6v-25fm-p4fg
- OSV: GHSA-2v6v-25fm-p4fg
- github.com/seaweedfs/seaweedfs/security/advisories/GHSA-2v6v-25fm-p4fg
- nvd.nist.gov/vuln/detail/CVE-2026-72920
- github.com/seaweedfs/seaweedfs/pull/9442
- github.com/seaweedfs/seaweedfs/commit/5e8f99f40a8abc7b449aefd260516443377041c7
- github.com/seaweedfs/seaweedfs
- github.com/seaweedfs/seaweedfs/releases/tag/4.24