SeaweedFS: Filer JWT allowed_prefixes literal prefix match allows cross-tenant access to sibling paths — GHSA-GV5W-HFX8-8CWQ

Summary

### 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…

Timeline

Published by source

2026-09-02

Risk context

• Reported severity or threat level: high.
• Reported CVSS score: 8.1 out of 10.
• Reported EPSS value: 0.00238.
• Review exposure for the affected product or family: go: github.com/seaweedfs/seaweedfs.

Product

go: github.com/seaweedfs/seaweedfs

What to do

General, cautious steps (verify details in the official source):

• Prioritize patching or mitigation immediately (treat as actively risky).
• Identify affected product versions in your inventory and verify whether you are impacted.
• Apply vendor patches/updates or recommended mitigations as soon as available.
• Read the official advisory for exact affected versions and remediation steps.

Official advisory

• Read the official source
• CVE Record
• NVD

Evidence and provenance

Canonical advisory ID

GHSA-GV5W-HFX8-8CWQ

Source

GitHub

Vendor

GitHub

Published by source

2026-09-02

Last source activity

2026-09-02

Additional identifiers

CVE-2026-72921

Curated by

hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.