Is CVE-2026-72920 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-72920 being exploited in the wild.

How severe is CVE-2026-72920?

Critical severity, with a CVSS score of 9.8, published 2 September 2026.

Which products and versions are affected?

github.com/seaweedfs/seaweedfs (Go) < 0.0.0-20260512171108-5e8f99f40a8a, SEMVER:introduced=0,fixed=0.0.0-20260512171108-5e8f99f40a8a; SeaweedFS < 4.24.

Is there a fix for CVE-2026-72920?

Yes. github.com/seaweedfs/seaweedfs (Go): upgrade to 0.0.0-20260512171108-5e8f99f40a8a or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-72920 attacked?

It is attacked over the network.

Am I affected by CVE-2026-72920?

Check whether you run github.com/seaweedfs/seaweedfs (Go) or SeaweedFS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-72920: SeaweedFS unauthenticated filer IAM gRPC service authentication bypass

Q: Is there a fix for CVE-2026-72920?

Yes. github.com/seaweedfs/seaweedfs (Go): upgrade to 0.0.0-20260512171108-5e8f99f40a8a or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-72920 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-72920?

Check whether you run github.com/seaweedfs/seaweedfs (Go) or SeaweedFS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-72920 · Severity: critical · CVSS 9.8 · Published 2026-09-02

SeaweedFS is a distributed object storage system that provides S3-compatible access to files. The filer service's IAM gRPC endpoint was exposed without authentication, allowing any network-accessible attacker to create administrative credentials and gain full control over all stored data. An attacker can read, modify, or delete any object in the storage system without providing any credentials.

Technologies: github.com/seaweedfs/seaweedfs (Go), SeaweedFS. Vendors: Go, SeaweedFS.

Quick answers

Is CVE-2026-72920 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-72920 being exploited in the wild.
How severe is CVE-2026-72920?: Critical severity, with a CVSS score of 9.8, published 2 September 2026.
Which products and versions are affected?: github.com/seaweedfs/seaweedfs (Go) < 0.0.0-20260512171108-5e8f99f40a8a, SEMVER:introduced=0,fixed=0.0.0-20260512171108-5e8f99f40a8a; SeaweedFS < 4.24.
Is there a fix for CVE-2026-72920?: Yes. github.com/seaweedfs/seaweedfs (Go): upgrade to 0.0.0-20260512171108-5e8f99f40a8a or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-72920 attacked?: It is attacked over the network.
Am I affected by CVE-2026-72920?: Check whether you run github.com/seaweedfs/seaweedfs (Go) or SeaweedFS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/seaweedfs/seaweedfs (Go): upgrade to 0.0.0-20260512171108-5e8f99f40a8a or later
```
go get github.com/seaweedfs/seaweedfs@v0.0.0-20260512171108-5e8f99f40a8a
```

Technical details

The vulnerability is a missing authentication check in the filer's IAM gRPC service (`SeaweedIdentityAccessManagement`). The service exposes administrative RPCs including `CreateUser`, `CreateAccessKey`, and `PutUserPolicy` without requiring any credentials. Any client with network access to the filer gRPC port can invoke these functions to mint S3 administrative access keys and grant themselves full privileges. The issue affects all versions before 4.24; JWT signing keys and mTLS listener-level ACLs do not close the gap as they were not integrated with the IAM service RPCs. The fix in version 4.24 adds Bearer token authentication signed with the filer admin signing key (`jwt.filer_signing.key`) to all IAM RPCs and requires the signing key to be configured.

Affected products

SeaweedFS SeaweedFS < 4.24

Identifiers

CVE-2026-72920
GHSA-2v6v-25fm-p4fg
GO-2026-6351

Timeline

2026-09-02: disclosed: Published to GitHub Advisory Database
2026-08-11: advisory: Published to NVD
2026-05-12: patched: Fixed in version 4.24

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.