Cross-tenant access via literal path-prefix authorization
Published Aug 11, 2026 · Updated Aug 11, 2026
Incorrect authorization in SeaweedFS before 4.24 allows remote authenticated users to read and write sibling tenants' data with a scoped filer JWT. The allowed_prefixes check in weed/server/filer_server_handlers.go applies strings.HasPrefix to raw request paths rather than comparing normalized path components. A valid token limited to /tenant1 therefore reaches sibling paths such as /tenant1234, crossing the configured tenant boundary without affecting service availability.
Summary
What happened
Incorrect authorization in SeaweedFS before 4.24 allows remote authenticated users to read and write sibling tenants' data with a scoped filer JWT. The allowed_prefixes check in weed/server/filer_server_handlers.go applies strings.HasPrefix to raw request paths rather than comparing normalized path components. A valid token limited to /tenant1 therefore reaches sibling paths such as /tenant1234, crossing the configured tenant boundary without affecting service availability.
The record
- CVE
- CVE-2026-72921
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- SeaweedFS
- Product
- SeaweedFS
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.24
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo