Authorization Flaw in github.com/seaweedfs/seaweedfs (CVE-2026-72921)
Summary
Vulnerability in github.com/seaweedfs/seaweedfs (CVE-2026-72921). Confidential information can be exposed externally. Exploitable via allowed_prefixes. Mitigation: upgrade to 0.0.0-20260512171048-05ed5c9ae8a2 or later.
Original description
The description as published by the source.
SeaweedFS is a distributed storage system. Prior to 4.24, the weed/server/filer_server_handlers.go allowed_prefixes authorization check used strings.HasPrefix on raw path strings, so a filer JWT scoped to /tenant1 also authorized sibling paths such as /tenant1234, /tenant1-old, and /tenant1backup, enabling cross-tenant reads and writes with a valid scoped token. This issue is fixed in version 4.24.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-72921 has been found in github.com/seaweedfs/seaweedfs.
Attackers can target a specific entry point like allowed_prefixes over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260512171048-05ed5c9ae8a2 or later.
If unsure, ask your IT team or search "github.com/seaweedfs/seaweedfs CVE-2026-72921" on the vendor's site.
CVE-2026-72921 (github.com/seaweedfs/seaweedfs) — CWE-863 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: allowed_prefixes / strings.HasPrefix / path.Clean
Patched: 0.0.0-20260512171048-05ed5c9ae8a2 — apply immediately
Workaround: Where feasible, choose prefix names that are not string-prefixes of one another (e.g.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in github.com/seaweedfs/seaweedfs. Attackers reach the vulnerable code path via allowed_prefixes.
Check the vendor advisory for the affected versions of github.com/seaweedfs/seaweedfs. Attack surface: allowed_prefixes / strings.HasPrefix / path.Clean.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 0.0.0-20260512171048-05ed5c9ae8a2.
Workaround: Where feasible, choose prefix names that are not string-prefixes of one another (e.g.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/seaweedfs/seaweedfs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/seaweedfs/seaweedfs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/seaweedfs/seaweedfsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Where feasible, choose prefix names that are not string-prefixes of one another (e.g.パッチが適用されるまでの応急処置として、Where feasible, choose prefix names that are not string-prefixes of one another (e.g. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260512171048-05ed5c9ae8a2ステージング環境で 0.0.0-20260512171048-05ed5c9ae8a2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com