Advisory record · GHSA-gv5w-hfx8-8cwq

SeaweedFS: Filer JWT allowed_prefixes literal prefix match allows cross-tenant access to sibling paths

CVSS 8.1 HighEPSS 0.0043 · 37th percentile

Published by the GitHub Advisory Database at 2 Sept 2026, 23:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/seaweedfs/seaweedfsGo<0.0.0-20260512171048-05ed5c9ae8a20.0.0-20260512171048-05ed5c9ae8a2
Identifiers
GHSA-gv5w-hfx8-8cwq · BIT-seaweedfs-2026-72921 · CVE-2026-72921 · GO-2026-6361
Weakness (CWE)
CWE-863
Published
2 Sept 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

SeaweedFS filer JWTs that restrict access with allowed_prefixes match paths by literal string prefix, so a token scoped to /tenant1 also authorizes sibling paths such as /tenant1234. An attacker holding a valid scoped token for one tenant can read and write another tenant's data in a multi-tenant deployment. Upgrade to 4.24, which matches path components instead of raw string prefixes.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0043, the 37th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.