← Back
CVE-2026-54917
critical
CVSS 10.0
Path Traversal in seaweedfs (CVE-2026-54917)
Summary
path traversal in seaweedfs (CVE-2026-54917). Confidential information can be exposed externally. Exploitable via `GET /bucket-A/../evil-bucket/key`. Mitigation: upgrade to `4.30` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54917** has been found in seaweedfs.
Attackers can target a specific entry point like `GET /bucket-A/../evil-bucket/key` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 10.0/10.
What to do: upgrade seaweedfs to **4.30** or later.
If unsure, ask your IT team or search "seaweedfs CVE-2026-54917" on the vendor's site.
CVE-2026-54917 (seaweedfs) — CWE-22 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /bucket-A/../evil-bucket/key
Patched: `4.30` — apply immediately
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.
❓ What is the problem
**Path traversal** (CWE-22) exists in seaweedfs. Attackers reach the vulnerable code path via `GET /bucket-A/../evil-bucket/key` without authentication.
📍 Affected scope
seaweedfs — . Attack surface: GET /bucket-A/../evil-bucket/key.
🔥 Severity
Severity: Critical (CVSS 10.0/10). Confidential information can be exposed externally
🔧 How to fix
Update to **4.30**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `GET /bucket-A/../evil-bucket/key` requests with malformed payloads or SQL meta-characters. Run `grep -r 'seaweedfs' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'seaweedfs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `seaweedfs` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /bucket-A/../evil-bucket/key' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /bucket-A/../evil-bucket/key` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade seaweedfs to 4.30ステージング環境で 4.30 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /bucket-A/../evil-bucket/key on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- exploit 134c704f-9b21-4f2e-91b3-4a467353bcc0
- issue [email protected]