pyLoad has an Arbitrary File Write via Path Traversal in edit_package()

Exploitation

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

CVSS

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

EPSS

• CVE-2026-29778: 0.57% estimated exploitation activity in the next 30 days; percentile 47.27 (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.

The editpackage() function implements insufficient sanitization for the packfolder parameter. The current protection relies on a single-pass string replacement of "../", which can be bypassed using crafted recursive traversal sequences. Exploitation An authenticated user with MODIFY permission can bypass the sanitization by submitting a payload such as: packfolder=..././..././..././tmp After the single-pass replacement, this becomes: ../../../tmp Because the traversal sequences are not properly validated, the resulting normalized path escapes the intended storage directory and writes files to /tmp or other locations.

Published by the source

5 Mar 2026, 00:32 UTC

Last modified by the source

8 Jun 2026, 19:15 UTC

Source last checked

26 Oct 2026, 13:44 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6px9-j4qr-xfjw

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6px9-j4qr-xfjw

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

# Patch Next advisory brief: CVE-2026-29778

Advisory: pyLoad has an Arbitrary File Write via Path Traversal in edit_package()
IDs: CVE-2026-29778, GHSA-6px9-j4qr-xfjw
Record: https://patchnext.com/advisories/cve-2026-29778 (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: High (CVSS 7.1)
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.dev97. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pyload-ng: affected >= 0.5.0b3.dev13, <= 0.5.0b3.dev96; fixed in 0.5.0b3.dev97

## 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-6px9-j4qr-xfjw (OSV record GHSA-6px9-j4qr-xfjw lists affected ranges: PyPI pyload-ng >=0.5.0b3.dev13 <0.5.0b3.dev97 (fixed))
- Verified: https://github.com/advisories/GHSA-6px9-j4qr-xfjw (GitHub-reviewed advisory GHSA-6px9-j4qr-xfjw lists affected ranges: PyPI pyload-ng >=0.5.0b3.dev13 <=0.5.0b3.dev96)

Commands are suggestions: review each one before running it.