Path Traversal in github.com/seaweedfs/seaweedfs (CVE-2026-55874)
Summary
Path traversal in github.com/seaweedfs/seaweedfs (CVE-2026-55874). Confidential information can be exposed externally. Exploitable via CopyObject. Mitigation: upgrade to 0.0.0-20260612000715-b44cf51fe931 or later.
Original description
The description as published by the source.
SeaweedFS: Path traversal in the S3 gateway X-Amz-Copy-Source header allows cross-bucket object read in github.com/seaweedfs/seaweedfs
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-55874 has been found in github.com/seaweedfs/seaweedfs.
Attackers can target a specific entry point like CopyObject over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260612000715-b44cf51fe931 or later.
If unsure, ask your IT team or search "github.com/seaweedfs/seaweedfs CVE-2026-55874" on the vendor's site.
CVE-2026-55874 (github.com/seaweedfs/seaweedfs) — CWE-22 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: CopyObject / UploadPartCopy / Read / Write
Patched: 0.0.0-20260612000715-b44cf51fe931 — apply immediately
Workaround: No configuration workaround.
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.
Path traversal (CWE-22) exists in github.com/seaweedfs/seaweedfs. Attackers reach the vulnerable code path via CopyObject.
Check the vendor advisory for the affected versions of github.com/seaweedfs/seaweedfs. Attack surface: CopyObject / UploadPartCopy / Read / Write.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 0.0.0-20260612000715-b44cf51fe931.
Workaround: No configuration workaround.
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
No configuration workaround.パッチが適用されるまでの応急処置として、No configuration workaround. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260612000715-b44cf51fe931ステージング環境で 0.0.0-20260612000715-b44cf51fe931 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com