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

Advisory record · `GHSA-gv5w-hfx8-8cwq`

- **Identifiers:** `GHSA-gv5w-hfx8-8cwq` · `BIT-seaweedfs-2026-72921` · `CVE-2026-72921` · `GO-2026-6361`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 2 Sept 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/seaweedfs/seaweedfs` (Go): affected `<0.0.0-20260512171048-05ed5c9ae8a2`; fixed in `0.0.0-20260512171048-05ed5c9ae8a2`

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

- 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`, from 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

- 31 Oct 2026, 14:13 UTC: First seen by agentprime
- 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-gv5w-hfx8-8cwq)

## Sources

- [GitHub Advisory Database: GHSA-gv5w-hfx8-8cwq](https://github.com/advisories/GHSA-gv5w-hfx8-8cwq)
- [OSV: GHSA-gv5w-hfx8-8cwq](https://osv.dev/vulnerability/GHSA-gv5w-hfx8-8cwq)
- <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>
- <https://github.com/seaweedfs/seaweedfs/releases/tag/4.24>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gv5w-hfx8-8cwq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gv5w-hfx8-8cwq/>. Everything for agents: <https://agentprime.io/llms.txt>.
