Vulnerability in github.com/seaweedfs/seaweedfs (CVE-2026-72920)
Summary
Vulnerability in github.com/seaweedfs/seaweedfs (CVE-2026-72920). Successful exploitation can lead to full system takeover. Exploitable via SeaweedIdentityAccessManagement. Mitigation: upgrade to 0.0.0-20260512171108-5e8f99f40a8a or later.
Original description
The description as published by the source.
SeaweedFS is a distributed storage system. Prior to 4.24, the filer registers the SeaweedIdentityAccessManagement gRPC service without mandatory authentication when jwt.filer_signing.key is unset, allowing any client that can reach the filer gRPC port to invoke CreateUser, CreateAccessKey, PutPolicy, and related IAM RPCs to mint credentials and gain S3 administrative control. This issue is fixed in versions 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-72920 has been found in github.com/seaweedfs/seaweedfs.
Attackers can target a specific entry point like SeaweedIdentityAccessManagement over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260512171108-5e8f99f40a8a or later.
If unsure, ask your IT team or search "github.com/seaweedfs/seaweedfs CVE-2026-72920" on the vendor's site.
CVE-2026-72920 (github.com/seaweedfs/seaweedfs) — CWE-306 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: SeaweedIdentityAccessManagement / CreateUser / CreateAccessKey / PutUserPolicy
Patched: 0.0.0-20260512171108-5e8f99f40a8a — apply immediately
Workaround: Restrict the filer gRPC port to trusted hosts.
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.
A vulnerability (CWE-306) exists in github.com/seaweedfs/seaweedfs. Attackers reach the vulnerable code path via SeaweedIdentityAccessManagement without authentication.
Check the vendor advisory for the affected versions of github.com/seaweedfs/seaweedfs. Attack surface: SeaweedIdentityAccessManagement / CreateUser / CreateAccessKey / PutUserPolicy.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 0.0.0-20260512171108-5e8f99f40a8a.
Workaround: Restrict the filer gRPC port to trusted hosts.
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
Restrict the filer gRPC port to trusted hosts.パッチが適用されるまでの応急処置として、Restrict the filer gRPC port to trusted hosts. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260512171108-5e8f99f40a8aステージング環境で 0.0.0-20260512171108-5e8f99f40a8a に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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