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

> Attackers can gain S3 administrative control by invoking unauthenticated IAM gRPC services when JWT signing keys are not configured.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** BIT-seaweedfs-2026-72920, GHSA-2v6v-25fm-p4fg, GO-2026-6351, MINI-24w3-9649-75j4, MINI-qcv7-976x-rw6h

## What is CVE-2026-72920?

CVE-2026-72920 is a critical missing authorization vulnerability in seaweedfs, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-72920?

4 open source packages ship an affected version, including github.com/seaweedfs/seaweedfs and seaweedfs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/seaweedfs/seaweedfs` | Go | All versions | 0.0.0-20260512171108-5e8f99f40a8a |
| `github.com/seaweedfs/seaweedfs` | Go | All versions | 0.0.0-20260512171108-5e8f99f40a8a |
| `github.com/seaweedfs/seaweedfs` | Go | All versions | 0.0.0-20260512171108-5e8f99f40a8a |
| `seaweedfs` | Bitnami | All versions | 4.24.0 |

## How do I fix CVE-2026-72920?

Upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260512171108-5e8f99f40a8a or later.

## Is CVE-2026-72920 being exploited?

There is no known exploitation of CVE-2026-72920 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72920 and fix it if it is affected.

What it is: CVE-2026-72920 is a critical missing authorization vulnerability in seaweedfs, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72920 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/seaweedfs/seaweedfs (Go): affected all versions; fixed in 0.0.0-20260512171108-5e8f99f40a8a
- github.com/seaweedfs/seaweedfs (Go): affected all versions; fixed in 0.0.0-20260512171108-5e8f99f40a8a
- github.com/seaweedfs/seaweedfs (Go): affected all versions; fixed in 0.0.0-20260512171108-5e8f99f40a8a
- seaweedfs (Bitnami): affected all versions; fixed in 4.24.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72920/ (Markdown: https://insights.sbomify.com/CVE-2026-72920/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72920
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72920
- OSV: https://osv.dev/vulnerability/CVE-2026-72920

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72920/
Summaries are generated and may contain mistakes; the official description above is the record.