---
title: "CVE-2026-72920: SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control"
url: https://erroneo.us/security/cve/CVE-2026-72920/
description: "CVE-2026-72920 (github.com/seaweedfs/seaweedfs (Go)): SeaweedFS is a distributed storage system. Prior to 4.24, the filer registers the…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-08-11
date_modified: 2026-09-02
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-72920"
kev: false
cvss: 9.8
epss: 0.00779
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-72920: SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.8% , percentile 55: FIRST’s model estimates a 0.8% chance of exploitation activity in the next 30 days, higher than 55% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes github.com/seaweedfs/seaweedfs (Go) < 0.0.0-20260512171108-5e8f99f40a8a, fixed in 0.0.0-20260512171108-5e8f99f40a8a . Check your lockfile, including transitive dependencies.

## What it is

SeaweedFS is a distributed storage system. Prior to 4.24, the filer registers the SeaweedIdentityAccessManagement gRPC service without mandatory authentication when jwt.filersigning.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.

## Affected packages

- Go `github.com/seaweedfs/seaweedfs` < 0.0.0-20260512171108-5e8f99f40a8a → fixed: 0.0.0-20260512171108-5e8f99f40a8a

## Affected products (CVE record)

- seaweedfs seaweedfs: < 4.24

## Severity

- GitHub_M CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`
- GitHub CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.78% probability of exploitation activity in the next 30 days; percentile 55.

## Sources

- [GitHub Advisory GHSA-2v6v-25fm-p4fg](https://github.com/advisories/GHSA-2v6v-25fm-p4fg)
- [CVE.org record CVE-2026-72920](https://www.cve.org/CVERecord?id=CVE-2026-72920)
- [NVD entry CVE-2026-72920](https://nvd.nist.gov/vuln/detail/CVE-2026-72920)
- [github.com](https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-2v6v-25fm-p4fg)
- [github.com](https://github.com/seaweedfs/seaweedfs/pull/9442)
- [github.com](https://github.com/seaweedfs/seaweedfs/commit/5e8f99f40a8abc7b449aefd260516443377041c7)
- [github.com](https://github.com/seaweedfs/seaweedfs/releases/tag/4.24)

---
Source page: https://erroneo.us/security/cve/CVE-2026-72920/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt