CVE-2026-72921: SeaweedFS: Filer JWT allowed_prefixes literal prefix match allows cross-tenant access to sibling paths
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.
References
- github.com/advisories/GHSA-gv5w-hfx8-8cwq
- github.com/seaweedfs/seaweedfs/commit/05ed5c9ae8a2a45101b52b61d02f170d20d587ff
- github.com/seaweedfs/seaweedfs/pull/9439
- github.com/seaweedfs/seaweedfs/releases/tag/4.24
- github.com/seaweedfs/seaweedfs/security/advisories/GHSA-gv5w-hfx8-8cwq
- nvd.nist.gov/vuln/detail/CVE-2026-72921
Code Behaviors & Features
Detect and mitigate CVE-2026-72921 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →