Summary No sanitization of package folder name allows writing files anywhere outside the intended download directory. Affected Component src/pyload/core/api/__init__.py Function: set_package_data() Details When passing…
| CVE ID | CVE-2026-42315 |
| Vendor | pip |
| Affected Product | pyload-ng |
| Vulnerability Type | Vulnerability |
| CVSS Score | 8.1 (HIGH) |
| Actively Exploited | ❌ No known exploitation |
| Patch Status | See Vendor Advisory → |
| Reported By | CYBERDUDEBIVASH SENTINEL APEX Intelligence (via github_advisories) |
#
No sanitization of package folder name allows writing files anywhere outside the intended download directory.
src/pyload/core/api/__init__.pyset_package_data()When passing a folder name in the set_package_data() API function call inside the data object with key "_folder", there is no sanitization at all, allowing a user with Perms.MODIFY to specify arbitrary directories as download locations for a package.
1) Create a package, note response package ID e.g. 5 ``` curl -X 'POST' \ 'http://localhost:8000/api/add_package' \ -H 'accept: application/json' \ -H 'X-API-Key: ' \ -H 'Content-Type: application/json' \ -d '{ "name": "set_package_data_exploit_poc", "links": [ "http://example.com/file.txt" ], "dest": 1 }
Sigma rules, YARA signatures, IOC table, and SIEM queries for Splunk, Elastic, Sentinel, and Chronicle — deployable in 5 minutes.