CVE-2026-72921: SeaweedFS: Filer JWT allowed_prefixes literal prefix match allows cross-tenant access to sibling paths
Impact When a filer JWT restricts a token to a set of path prefixes via allowedprefixes, the authorization check used a literal byte-prefix match (strings.HasPrefix). A token scoped to /tenant1 therefore also authorized requests to sibling paths such as /tenant1234, /tenant1-old, and /tenant1backup. In a multi-tenant deployment this lets the holder of one tenant's token access another tenant's data.
Published Sep 2, 2026
Affected packages
github.com/seaweedfs/seaweedfs
- Ecosystem
- Go
- Affected
- < 0.0.0-20260512171048-05ed5c9ae8a2
- Fixed in
- 0.0.0-20260512171048-05ed5c9ae8a2
- Check
go list -m github.com/seaweedfs/seaweedfs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
When a filer JWT restricts a token to a set of path prefixes via allowed_prefixes, the authorization check used a literal byte-prefix match (strings.HasPrefix). A token scoped to /tenant1 therefore also authorized requests to sibling paths such as /tenant1234, /tenant1-old, and /tenant1backup.
In a multi-tenant deployment this lets the holder of one tenant's token access another tenant's data. Because allowed_prefixes gates both read and write tokens, the impact covers cross-tenant reads and writes. A valid scoped token is required, so this is an authorization bypass rather than a fully unauthenticated flaw.
Affected component
weed/server/filer_server_handlers.go(JWTallowed_prefixesauthorization check)
Patches
Fixed in 4.24. The check now matches on /-separated path components after path.Clean normalisation, so /tenant1 authorizes only /tenant1 and its descendants — not /tenant1234 or other sibling paths.
Workarounds
Where feasible, choose prefix names that are not string-prefixes of one another (e.g. keep a trailing separator convention). Upgrade to 4.24.
References
- Reported by Kadir Arslan (https://github.com/KadirArslan)
Credited to KadirArslan.
References
- https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-gv5w-hfx8-8cwq
- https://nvd.nist.gov/vuln/detail/CVE-2026-72921
- https://github.com/seaweedfs/seaweedfs/pull/9439
- https://github.com/seaweedfs/seaweedfs/commit/05ed5c9ae8a2a45101b52b61d02f170d20d587ff
- https://github.com/seaweedfs/seaweedfs/releases/tag/4.24
- https://github.com/advisories/GHSA-gv5w-hfx8-8cwq
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-72920
SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control
critical9.8Sep 2, 2026CVE-2026-55873
SeaweedFS: Improper authorization in the S3Tables / Iceberg REST management API lets a low-privileged S3 user enumerate administrator-owned table buckets
medium4.3Aug 28, 2026CVE-2026-55874
SeaweedFS: Path traversal in the S3 gateway X-Amz-Copy-Source header allows cross-bucket object read
high7.7Aug 28, 2026CVE-2026-54917
SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access
high7.8Aug 12, 2026CVE-2026-73080
SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle
critical9.3Aug 11, 2026CVE-2024-40120
SeaweedFS Vulnerable to SQL Injection
medium6.5May 16, 2025
