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.
CVE-2026-70657
This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(medium)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 19, 2026
Advisory Details (3)
Auto-updated Aug 18, 2026file/dirkey confusion · Advisory · 9001/copyparty · GitHub
https://github.com/9001/copyparty/security/advisories/GHSA-x5pq-m9p8-f4vxSECURITY: fix dirkeys
Patch available: 9001/copyparty v1.20.17
https://github.com/9001/copyparty/releases/tag/v1.20.17commit e40755331ba9 (9001/copyparty)
Fix landed in 9001/copyparty commit e40755331ba9 — awaiting tagged release
https://github.com/9001/copyparty/commit/e40755331ba9449993ff482456e6bdd2c6deb950Vendor Advisories for CVE-2026-70657(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| copyparty | 0.10.0 ... 1.9.9 (373 versions) | 1.20.17 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 17:38 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 16:22 UTCEG score recompute
- 2026-08-18 18:25 UTCEG score recompute
- 2026-08-18 18:15 UTCEG score recompute
- 2026-08-18 15:19 UTCEG score recompute
- 2026-08-18 15:07 UTCEG score recompute
- 2026-08-18 15:04 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-70657?
When was CVE-2026-70657 disclosed?
Is CVE-2026-70657 actively exploited?
What is the CVSS score of CVE-2026-70657?
How do I remediate CVE-2026-70657?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70657
Is Your Infrastructure Affected by CVE-2026-70657?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.