Authenticated arbitrary-directory writes via unsanitized folder name
Published May 11, 2026 · Updated May 11, 2026
Path traversal in pyLoad before 0.5.0b3.dev100 allows remote authenticated users to place package downloads in arbitrary directories. The set_package_data() API in src/pyload/core/api/init.py accepts the _folder field without sanitizing or constraining it to the download directory. Perms.MODIFY access and filesystem write permission for the pyLoad process are required, and successful exploitation redirects package output outside the intended directory.
Summary
What happened
Path traversal in pyLoad before 0.5.0b3.dev100 allows remote authenticated users to place package downloads in arbitrary directories. The set_package_data() API in src/pyload/core/api/init.py accepts the _folder field without sanitizing or constraining it to the download directory. Perms.MODIFY access and filesystem write permission for the pyLoad process are required, and successful exploitation redirects package output outside the intended directory.
The record
- CVE
- CVE-2026-42315
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- pyLoad
- Product
- pyLoad
- Classifications
- CWE-22, CWE-36, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 11, 2026CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.5.0b3.dev100
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA set_package_data API proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo