CVE-2026-72921

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

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 (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 11, 2026

Last Modified

September 9, 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 pull request

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 advisoryMentions a patch (unverified)

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

Vendor Advisories for CVE-2026-72921(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 rangeFix by version rangeDependents
github.com/seaweedfs/seaweedfs—
  • every version up to 0.0.0-20260512171048-05ed5c9ae8a2: fixed in 0.0.0-20260512171048-05ed5c9ae8a2
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 112 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 15 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-10-13 08:04 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-10-12 15:41 UTCEG score recompute
  5. 2026-10-11 19:27 UTCEG score recompute
  6. 2026-10-11 16:42 UTCEG score recompute
  7. 2026-10-11 14:02 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-06 17:54 UTCEG score recompute
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-05 18:01 UTCEG score recompute
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-04 23:30 UTCEG score recompute
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-10-03 21:20 UTCEG score recompute
  20. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-02 22:26 UTCEG score recompute
  22. 2026-10-02 08:43 UTCEG score recompute
  23. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-09-30 22:18 UTCEG score recompute
  25. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 72 more
  1. 2026-09-29 05:14 UTCEG score recompute
  2. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-09-28 02:19 UTCEG score recompute
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-09-27 11:00 UTCEG score recompute
  6. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-09-25 03:55 UTCEG score recompute
  8. 2026-09-24 02:20 UTCEG score recompute
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  10. 2026-09-22 23:52 UTCEG score recompute
  11. 2026-09-21 21:12 UTCEG score recompute
  12. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  13. 2026-09-21 00:54 UTCEG score recompute
  14. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  15. 2026-09-19 19:50 UTCEG score recompute
  16. 2026-09-19 06:18 UTCEG score recompute
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  18. 2026-09-18 03:02 UTCEG score recompute
  19. 2026-09-17 00:34 UTCEG score recompute
  20. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  21. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-09-15 13:25 UTCEG score recompute
  23. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  24. 2026-09-13 18:25 UTCEG score recompute
  25. 2026-09-12 16:15 UTCEG score recompute
  26. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  27. 2026-09-12 03:11 UTCEG score recompute
  28. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-09-11 14:04 UTCEG score recompute
  30. 2026-09-10 10:07 UTCEG score recompute
  31. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  32. 2026-09-09 05:42 UTCEG score recompute
  33. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  34. 2026-09-07 17:02 UTCEG score recompute
  35. 2026-09-06 17:31 UTCEG score recompute
  36. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-09-06 04:26 UTCEG score recompute
  38. 2026-09-05 01:44 UTCEG score recompute
  39. 2026-09-04 08:18 UTCEG score recompute
  40. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-09-03 01:28 UTCEG score recompute
  42. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-09-02 02:45 UTCEG score recompute
  44. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-09-01 13:28 UTCEG score recompute
  46. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  47. 2026-08-31 00:57 UTCEG score recompute
  48. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  49. 2026-08-30 11:52 UTCEG score recompute
  50. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  51. 2026-08-29 09:41 UTCEG score recompute
  52. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  53. 2026-08-28 00:53 UTCEG score recompute
  54. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  55. 2026-08-26 21:57 UTCEG score recompute
  56. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  57. 2026-08-25 19:41 UTCEG score recompute
  58. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  59. 2026-08-24 17:26 UTCEG score recompute
  60. 2026-08-23 01:11 UTCEG score recompute
  61. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  62. 2026-08-22 12:06 UTCEG score recompute
  63. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  64. 2026-08-21 09:54 UTCEG score recompute
  65. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  66. 2026-08-19 18:41 UTCEG score recompute
  67. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  68. 2026-08-18 15:16 UTCEG score recompute
  69. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  70. 2026-08-18 01:18 UTCEG score recompute
  71. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  72. 2026-08-16 23:03 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-72921?
CVE-2026-72921 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-72921 published?
The CVE record for CVE-2026-72921 was published on August 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-72921 actively exploited?
CVE-2026-72921 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72921?
CVE-2026-72921 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72921?
A fix for CVE-2026-72921 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72921 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs