CVE-2026-72921 json
SeaweedFS: Filer JWT allowed_prefixes literal prefix match allows cross-tenant access to sibling paths
published 3mo ago modified 2mo ago also BIT-seaweedfs-2026-72921 , EUVD-2026-56159 , GHSA-gv5w-hfx8-8cwq , GO-2026-6361
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/seaweedfs/seaweedfs 0.0.0-20260512171048-05ed5c9ae8a2
- bitnami seaweedfs 4.24.0
- seaweedfs seaweedfs 4.24
- govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260916T180043-160000.1.1
suse advisories SUSE-SU-2026:23855-1SUSE-SU-2026:23863-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260916T180043-160000.1.1
opensuse advisories openSUSE-SU-2026:21897-1
Is CVE-2026-72921 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/seaweedfs/seaweedfs | <0.0.0-20260512171048-05ed5c9ae8a2 |
0.0.0-20260512171048-05ed5c9ae8a2 |
| bitnami | seaweedfs | <4.24.0 |
4.24.0 |
Affected products
- seaweedfs seaweedfs
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/seaweedfs/seaweedfs/pull/9439
web, patch
-
github.com
/seaweedfs/seaweedfs/commit/05ed5c9ae8a2a45101b52b61d02f170d20d587ff
web, patch
-
github.com
/seaweedfs/seaweedfs/security/advisories/GHSA-gv5w-hfx8-8cwq
web, advisory
-
github.com
/seaweedfs/seaweedfs/releases/tag/4.24
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-72921
advisory, web
-
github.com
/seaweedfs/seaweedfs
package
Sources
- CVE List CVE-2026-72921
- GitHub Advisory GHSA-gv5w-hfx8-8cwq
- NVD CVE-2026-72921
- OSV BIT-seaweedfs-2026-72921
- OSV GO-2026-6361
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.