Authorization Flaw in copyparty (CVE-2026-70657)
Summary
Vulnerability in copyparty (CVE-2026-70657). Risk of unauthorized operations or information disclosure. Exploitable via dks. Mitigation: upgrade to 1.20.17 or later.
Original description
The description as published by the source.
Copyparty is a portable file server. Prior to 1.20.17, copyparty volumes with the dk or dks directory-key flag combined with the fk or fka file-key flag can convert a valid file key into a directory key, granting read access to the containing folder. This vulnerability was only reachable if both types of keys (filekeys and dirkeys) were manually enabled in the volume flags simultaneously. This issue is fixed in version 1.20.17.
Source: GitHub Security Advisories (Global) 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-70657 has been found in copyparty.
Attackers can target a specific entry point like dks over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade copyparty to 1.20.17 or later.
If unsure, ask your IT team or search "copyparty CVE-2026-70657" on the vendor's site.
CVE-2026-70657 (copyparty) — CWE-863 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: dks / fka
Patched: 1.20.17 — 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.
Incorrect authorization (CWE-863) exists in copyparty. Attackers reach the vulnerable code path via dks.
Check the vendor advisory for the affected versions of copyparty. Attack surface: dks / fka.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.20.17.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'copyparty' . 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 'copyparty' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
copypartyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade copyparty to 1.20.17ステージング環境で 1.20.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- web github.com