Is CVE-2026-70657 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-70657 being exploited in the wild.

How severe is CVE-2026-70657?

Medium severity, with a CVSS score of 4.3, published 18 August 2026.

Which products and versions are affected?

copyparty (PyPI) < 1.20.17, ECOSYSTEM:introduced=0,fixed=1.20.17.

Is there a fix for CVE-2026-70657?

Yes. copyparty (PyPI): upgrade to 1.20.17 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-70657 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-70657?

Check whether you run copyparty (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-70657: Copyparty file/dirkey confusion authorization bypass

Q: Which products and versions are affected?

copyparty (PyPI) < 1.20.17, ECOSYSTEM:introduced=0,fixed=1.20.17.

Q: Is there a fix for CVE-2026-70657?

Yes. copyparty (PyPI): upgrade to 1.20.17 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-70657 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-70657?

Check whether you run copyparty (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-70657 · Severity: medium · CVSS 4.3 · Published 2026-08-18

Copyparty, a file-sharing and streaming application, contains an authorization flaw that allows a user with a valid file-access key to escalate their permissions and read an entire folder. This only affects deployments that explicitly enable both file-level and directory-level access controls simultaneously. An authenticated attacker could circumvent access restrictions and read files they should not have permission to access.

Technologies: copyparty (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-70657 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-70657 being exploited in the wild.
How severe is CVE-2026-70657?: Medium severity, with a CVSS score of 4.3, published 18 August 2026.
Which products and versions are affected?: copyparty (PyPI) < 1.20.17, ECOSYSTEM:introduced=0,fixed=1.20.17.
Is there a fix for CVE-2026-70657?: Yes. copyparty (PyPI): upgrade to 1.20.17 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-70657 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-70657?: Check whether you run copyparty (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

copyparty (PyPI): upgrade to 1.20.17 or later
```
pip install "copyparty>=1.20.17"
```

Technical details

The vulnerability is a type of authorization bypass (CWE-863) affecting Copyparty's access-control mechanism. When both filekeys (file-level access tokens) and dirkeys (directory-level access tokens) are enabled on the same volume via volflag configuration, an attacker with a valid filekey can manipulate it to be accepted as a dirkey, escalating their permissions from single-file access to full directory read access. The attack requires network access and authentication (a valid filekey), with no additional user interaction needed. The vulnerability affects Copyparty versions before 1.20.17, which contains the fix. Both filekey and dirkey features are disabled by default, limiting the affected deployment surface.

Affected products

9001 Copyparty < 1.20.17

Identifiers

CVE-2026-70657
GHSA-x5pq-m9p8-f4vx
PYSEC-2026-3660

Timeline

2026-07-06: disclosed: Initial disclosure
2026-07-06: patched: Version 1.20.17 released with fix
2026-08-18: advisory: Published to GitHub Advisory Database

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.