Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54917 critical CVSS 10.0

Path Traversal in github.com/seaweedfs/seaweedfs (CVE-2026-54917)

Summary

Path traversal in github.com/seaweedfs/seaweedfs (CVE-2026-54917). Confidential information can be exposed externally. Exploitable via GET /bucket-A/../evil-bucket/key. Mitigation: upgrade to 0.0.0-20260526080459-dd1b4287899e or later.

Original description

The description as published by the source.

SeaweedFS before 4.34 contains a path traversal vulnerability in the S3 gateway DeleteMultipleObjectsHandler that allows authenticated S3 principals with write access to a single bucket to delete arbitrary objects in other tenants' buckets by supplying object keys containing ../ sequences in the DeleteObjects XML request body. Attackers can bypass authorization controls through a confused deputy condition, as the validateRequestPath middleware only inspects URL-captured path variables and never examines request-body keys, allowing the filer path to collapse directory traversal sequences and resolve deletions outside the authorized bucket.

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-54917 has been found in github.com/seaweedfs/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 github.com/seaweedfs/seaweedfs to 0.0.0-20260526080459-dd1b4287899e or later.
If unsure, ask your IT team or search "github.com/seaweedfs/seaweedfs CVE-2026-54917" on the vendor's site.

CVE-2026-54917 (github.com/seaweedfs/seaweedfs) — CWE-22 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /bucket-A/../evil-bucket/key / GET /bucket-A/../evil-bucket/secret.txt / GET /bucket-A/ / util.JoinPath
Patched: 0.0.0-20260526080459-dd1b4287899e — apply immediately
Workaround: For deployments that cannot upgrade immediately, place a reverse proxy in front of the gateway that normalizes the request path and rejects requests whose path contains .., %2e%2e, or backslash sequences.
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 github.com/seaweedfs/seaweedfs. Attackers reach the vulnerable code path via GET /bucket-A/../evil-bucket/key without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/seaweedfs/seaweedfs. Attack surface: GET /bucket-A/../evil-bucket/key / GET /bucket-A/../evil-bucket/secret.txt / GET /bucket-A/ / util.JoinPath.

🔥 Severity

Severity: Critical (CVSS 10.0/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.0.0-20260526080459-dd1b4287899e.

🛡️ Workaround

Workaround: For deployments that cannot upgrade immediately, place a reverse proxy in front of the gateway that normalizes the request path and rejects requests whose path contains .., %2e%2e, or backslash sequences.

🔍 Detection

Search webserver/proxy logs for unusual GET /bucket-A/../evil-bucket/key requests with malformed payloads or SQL meta-characters. 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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt 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 があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply temporary workaround mitigate 
    For deployments that cannot upgrade immediately, place a reverse proxy in front of the gateway that normalizes the request path and rejects requests whose path contains `..`, `%2e%2e`, or backslash sequences.

    パッチが適用されるまでの応急処置として、For deployments that cannot upgrade immediately, place a reverse proxy in front of the gateway that normalizes the request path and rejects requests whose path contains .., %2e%2e, or backslash sequences. を実施。回避策の副作用 (機能低下) を確認した上で。

  4. 4
    Apply patch patch 
    Upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260526080459-dd1b4287899e

    ステージング環境で 0.0.0-20260526080459-dd1b4287899e に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  5. 5
    Post-deployment verification verify 
    Replay attack against GET /bucket-A/../evil-bucket/key on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/seaweedfs/seaweedfs
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20260526080459-dd1b4287899e"}]}]
Bitnami seaweedfs
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.34.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details