PyLoad Vulnerable to Path Traversal via Package Folder Name

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2026-42314: 0.34% estimated exploitation activity in the next 30 days; percentile 27.76 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Insufficient sanitization of package folder names allows writing files outside the intended download directory. Affected Component - src/pyload/core/api/init.py - Function: addpackage() Description Package folder names are sanitized using insufficient string replacement: The ../ replacement is bypassable. The pattern ....// becomes .. after replacement (partial removal), leaving .. which can be exploited when the path is later resolved by the OS. Proof of Concept Setup Exploit Verification Check where files would be written: Impact Authenticated users with ADD permission can: - Write files outside the download directory - Potentially overwrite system files (depending on permissions) - Clutter system directories with downloaded content

Published by the source

5 May 2026, 21:13 UTC

Last modified by the source

8 Jun 2026, 20:00 UTC

Source last checked

26 Oct 2026, 13:44 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-97r3-5w84-r4q8

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-97r3-5w84-r4q8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-42314

Advisory: PyLoad Vulnerable to Path Traversal via Package Folder Name
IDs: CVE-2026-42314, GHSA-97r3-5w84-r4q8
Record: https://patchnext.com/advisories/cve-2026-42314 (revision 2, source checked 26 Oct 2026, 13:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pyload-ng 0.5.0b3.dev100. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pyload-ng: affected <= 0.5.0b3.dev79; fixed in 0.5.0b3.dev100

## Suggested inspection (read-only)
- `python -m pip show pyload-ng`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pyload-ng.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-97r3-5w84-r4q8 (OSV record GHSA-97r3-5w84-r4q8 lists affected ranges: PyPI pyload-ng >=0 <0.5.0b3.dev100 (fixed))
- Verified: https://github.com/advisories/GHSA-97r3-5w84-r4q8 (GitHub-reviewed advisory GHSA-97r3-5w84-r4q8 lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev79)

Commands are suggestions: review each one before running it.