Quick answers
- Is CVE-2026-32109 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32109 being exploited in the wild.
- How severe is CVE-2026-32109?
- Low severity, with a CVSS score of 3.7, published 12 March 2026.
- Which products and versions are affected?
- copyparty (PyPI) < 1.20.12, ECOSYSTEM:introduced=0,fixed=1.20.12.
- Is there a fix for CVE-2026-32109?
- Yes. copyparty (PyPI): upgrade to 1.20.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-32109 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-32109?
- 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.12 or later
pip install "copyparty>=1.20.12"
Technical details
A Cross-Site Scripting (XSS) vulnerability exists in Copyparty due to improper neutralization of input during web page generation. If an attacker has read and write permissions, they can upload a file named '.prologue.html'. While executing JavaScript when directly accessing this file is intended, the vulnerability allows the file to be evaluated when a victim visits a crafted folder URL (e.g., '/folder/?b'). Exploitation requires the victim to click a specific link, and impact is mitigated by strict SameSite cookie policies, meaning the link must typically be clicked from a page served by the same server. If successful, the attacker can execute arbitrary JavaScript in the victim's session to manipulate files. This is fixed in version 1.20.12.
Affected products
- 9001 copyparty < 1.20.12
Identifiers
- CVE-2026-32109
- GHSA-rcp6-88mm-9vgf
- PYSEC-2026-32
Timeline
- 2026-03-11: disclosed
- 2026-03-12: advisory: GitHub Advisory published
- 2026-03-12: patched