GHSA-PHV8-WGJP-G4P9
Vulnerability from github – Published: 2026-10-15 20:16 – Updated: 2026-10-15 20:16The FTP and FTPS server -- if enabled -- would allow uploading to any folder that the copyparty process had permission to write to.
The FTP-server is default-disabled, and must be explicitly enabled in the config with global-option ftp or ftps to be affected. Additionally, SFTP was not affected at all; only FTP and FTPS.
This was not a full read/write path-traversal; it had the following limitations: * Only applied to uploads; it was not possible to read/download existing files in this manner. * The output filename was not fully controllable; a randomized suffix would always be appended to the filename. * Existing files could not be overwritten or appended to; only new files could be created. * Filesystem-permissions would prevent writing to system folders, as copyparty surely does not run as root in most deployments. * Copyparty itself will not execute arbitrary files as code by default, so this vulnerability could not be used to execute arbitrary code through copyparty.
The main concern is the potential effect on other unrelated software which is running on the same system.
The severity is assuming the worst case (SC:H/SI:H), that the same machine is running some unrelated software that will execute new arbitrarily-named files as code, and that the copyparty process has sufficient privileges to write files into the config-folder of that unrelated software.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "copyparty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.20.19"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-104102"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-15T20:16:38Z",
"nvd_published_at": "2026-10-12T19:16:36Z",
"severity": "MODERATE"
},
"details": "The FTP and FTPS server -- if enabled -- would allow uploading to any folder that the copyparty process had permission to write to.\n\nThe FTP-server is default-disabled, and must be explicitly enabled in the config with global-option `ftp` or `ftps` to be affected. Additionally, SFTP was not affected at all; only FTP and FTPS.\n\nThis was not a full read/write path-traversal; it had the following limitations:\n* Only applied to uploads; it was not possible to read/download existing files in this manner.\n* The output filename was not fully controllable; a randomized suffix would always be appended to the filename.\n* Existing files could not be overwritten or appended to; only new files could be created.\n* Filesystem-permissions would prevent writing to system folders, as copyparty surely does not run as root in most deployments.\n* Copyparty itself will not execute arbitrary files as code by default, so this vulnerability could not be used to execute arbitrary code through copyparty.\n\nThe main concern is the potential effect on other unrelated software which is running on the same system.\n\nThe severity is assuming the worst case (SC:H/SI:H), that the same machine is running some unrelated software that will execute new arbitrarily-named files as code, and that the copyparty process has sufficient privileges to write files into the config-folder of that unrelated software.",
"id": "GHSA-phv8-wgjp-g4p9",
"modified": "2026-10-15T20:16:38Z",
"published": "2026-10-15T20:16:38Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/9001/copyparty/security/advisories/GHSA-phv8-wgjp-g4p9"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-104102"
},
{
"type": "WEB",
"url": "https://github.com/9001/copyparty/commit/b331bb1c8c8cc306b91e4d94221969335a7a3e86"
},
{
"type": "PACKAGE",
"url": "https://github.com/9001/copyparty"
},
{
"type": "WEB",
"url": "https://github.com/9001/copyparty/releases/tag/v1.20.19"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:N",
"type": "CVSS_V4"
}
],
"summary": "copyparty FTP: upload outside defined volumes (limited path traversal)"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.