CVE-2026-72920

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

August 11, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Patch available. Sources: github_pr, github_release, github, github_commit.
github Patch Available

Unauthenticated filer IAM gRPC service grants S3 administrative control · Advisory · seaweedfs/seaweedfs · GitHub

https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-2v6v-25fm-p4fg
github_release Patch Available

4.24

Patch available: seaweedfs/seaweedfs 4.24

https://github.com/seaweedfs/seaweedfs/releases/tag/4.24
github_pr

filer: require admin-signed JWT on the IAM gRPC service

Fix merged in seaweedfs/seaweedfs PR #9442 on 2026-05-12 — awaiting tagged release

https://github.com/seaweedfs/seaweedfs/pull/9442
github_commit

commit 5e8f99f40a8a (seaweedfs/seaweedfs)

Fix landed in seaweedfs/seaweedfs commit 5e8f99f40a8a — awaiting tagged release

https://github.com/seaweedfs/seaweedfs/commit/5e8f99f40a8abc7b449aefd260516443377041c7

Vendor Advisories for CVE-2026-72920(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/seaweedfs/seaweedfs—0.0.0-20260512171108-5e8f99f40a8a—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-21 00:54 UTCEG score recompute
  2. 2026-09-20 20:16 UTCEPSS rescore
  3. 2026-09-19 17:16 UTCEG score recompute
  4. 2026-09-18 22:13 UTCEG score recompute
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 00:47 UTCEG score recompute
  7. 2026-09-17 00:34 UTCEG score recompute
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 06:08 UTCEG score recompute
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-15 06:30 UTCEG score recompute
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-13 20:05 UTCEG score recompute
  14. 2026-09-12 16:57 UTCEG score recompute
  15. 2026-09-12 15:02 UTCEPSS rescore
  16. 2026-09-11 17:55 UTCEG score recompute
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-11 14:04 UTCEG score recompute
  19. 2026-09-10 09:54 UTCEG score recompute
  20. 2026-09-10 09:35 UTCEPSS rescore
  21. 2026-09-09 05:42 UTCEG score recompute
  22. 2026-09-08 22:01 UTCEPSS rescore
  23. 2026-09-07 17:02 UTCEG score recompute
  24. 2026-09-06 17:02 UTCEG score recompute
  25. 2026-09-06 13:48 UTCEPSS rescore
Show 54 more
  1. 2026-09-05 17:47 UTCEG score recompute
  2. 2026-09-04 16:01 UTCEG score recompute
  3. 2026-09-04 08:18 UTCEG score recompute
  4. 2026-09-04 05:07 UTCEPSS rescore
  5. 2026-09-03 01:28 UTCEG score recompute
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-01 17:19 UTCEG score recompute
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 06:36 UTCEG score recompute
  10. 2026-09-01 04:40 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 19:57 UTCEG score recompute
  13. 2026-08-30 19:18 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 04:32 UTCEG score recompute
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-29 09:41 UTCEG score recompute
  18. 2026-08-28 21:42 UTCEPSS rescore
  19. 2026-08-27 15:09 UTCEG score recompute
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 18:52 UTCEG score recompute
  22. 2026-08-26 14:47 UTCEPSS rescore
  23. 2026-08-25 17:34 UTCEG score recompute
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-24 14:39 UTCEG score recompute
  26. 2026-08-24 10:48 UTCEG score recompute
  27. 2026-08-23 04:04 UTCEG score recompute
  28. 2026-08-23 00:19 UTCEPSS rescore
  29. 2026-08-22 01:06 UTCEG score recompute
  30. 2026-08-21 23:49 UTCEPSS rescore
  31. 2026-08-21 01:57 UTCEG score recompute
  32. 2026-08-20 22:56 UTCEPSS rescore
  33. 2026-08-19 18:41 UTCEG score recompute
  34. 2026-08-19 17:04 UTCEPSS rescore
  35. 2026-08-18 17:23 UTCEG score recompute
  36. 2026-08-18 13:49 UTCEPSS rescore
  37. 2026-08-18 13:49 UTCEPSS rescore
  38. 2026-08-17 17:34 UTCEG score recompute
  39. 2026-08-17 13:47 UTCEPSS rescore
  40. 2026-08-16 18:33 UTCEG score recompute
  41. 2026-08-16 14:56 UTCEPSS rescore
  42. 2026-08-16 14:56 UTCEPSS rescore
  43. 2026-08-16 03:11 UTCEG score recompute
  44. 2026-08-16 02:15 UTCEPSS rescore
  45. 2026-08-15 04:11 UTCEG score recompute
  46. 2026-08-15 01:31 UTCEPSS rescore
  47. 2026-08-14 01:20 UTCEG score recompute
  48. 2026-08-13 22:00 UTCEPSS rescore
  49. 2026-08-12 14:37 UTCEG score recompute
  50. 2026-08-12 13:51 UTCEPSS rescore
  51. 2026-08-11 15:35 UTCEG score recompute
  52. 2026-08-11 14:57 UTCEG score recompute
  53. 2026-08-11 14:32 UTCEG score recompute
  54. 2026-08-11 14:31 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72920?
CVE-2026-72920 is a critical vulnerability published on August 11, 2026. 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,…
When was CVE-2026-72920 disclosed?
CVE-2026-72920 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72920 actively exploited?
CVE-2026-72920 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.2% of all scored CVEs.
What is the CVSS score of CVE-2026-72920?
CVE-2026-72920 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72920?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72920, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-72920

Explore →

Is Your Infrastructure Affected by CVE-2026-72920?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs