CVE-2026-72921

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% 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
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: 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 weed/server/filer_server_handlers.go allowed_prefixes authorization check used strings.HasPrefix on raw path strings, so a filer JWT scoped to /tenant1 also authorized sibling paths such as /tenant1234, /tenant1-old, and /tenant1backup, enabling cross-tenant reads and writes with a valid scoped token. This issue is fixed in version 4.24.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 13, 2026

Advisory Details (4)

Auto-updated Aug 11, 2026
Patch available. Sources: github_commit, github_release, github, github_pr.
github_release Patch Available

4.24

Patch available: seaweedfs/seaweedfs 4.24

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

commit 05ed5c9ae8a2 (seaweedfs/seaweedfs)

Fix landed in seaweedfs/seaweedfs commit 05ed5c9ae8a2 — awaiting tagged release

https://github.com/seaweedfs/seaweedfs/commit/05ed5c9ae8a2a45101b52b61d02f170d20d587ff
github_pr

filer: scope JWT allowed_prefixes to path components

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

https://github.com/seaweedfs/seaweedfs/pull/9439
github Patch Available

Filer JWT allowed_prefixes literal prefix match allows cross-tenant access to sibling paths · Advisory · seaweedfs/seaweedfs · GitHub

https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-gv5w-hfx8-8cwq

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 09:41 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-28 00:53 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 21:57 UTCEG score recompute
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-25 19:41 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 17:26 UTCEG score recompute
  11. 2026-08-23 01:11 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 12:06 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 09:54 UTCEG score recompute
  16. 2026-08-20 22:56 UTCEPSS rescore
  17. 2026-08-19 18:41 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 15:16 UTCEG score recompute
  20. 2026-08-18 13:49 UTCEPSS rescore
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 01:18 UTCEG score recompute
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 23:03 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 14 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 09:58 UTCEG score recompute
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 07:49 UTCEG score recompute
  5. 2026-08-15 01:31 UTCEPSS rescore
  6. 2026-08-14 05:40 UTCEG score recompute
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 16:35 UTCEG score recompute
  9. 2026-08-13 15:34 UTCEG score recompute
  10. 2026-08-12 17:44 UTCEG score recompute
  11. 2026-08-12 13:51 UTCEPSS rescore
  12. 2026-08-11 15:35 UTCEG score recompute
  13. 2026-08-11 14:32 UTCEG score recompute
  14. 2026-08-11 14:31 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72921?
CVE-2026-72921 is a high vulnerability published on August 11, 2026. SeaweedFS is a distributed storage system. Prior to 4.24, the weed/server/filerserverhandlers.go allowed_prefixes authorization check used strings.HasPrefix on raw path strings, so a filer JWT scoped to /tenant1 also authorized sibling paths such as /tenant1234, /tenant1-old, and /tenant1backup,…
When was CVE-2026-72921 disclosed?
CVE-2026-72921 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72921 actively exploited?
CVE-2026-72921 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 85.3% of all scored CVEs.
What is the CVSS score of CVE-2026-72921?
CVE-2026-72921 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-72921?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72921, 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

Explore the affected products and dependency analysis for CVE-2026-72921

Explore →

Is Your Infrastructure Affected by CVE-2026-72921?

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

Start Free Scan →Browse All CVEs