Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 5.3

How to Fix CVE-2026-35592: pyload (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

⚡ At a glance
SeverityCVSS 5.3, Medium
Actively exploited?No
Affectedpyload (< 0.5.0b3.dev97)
Fixed inSame patched build as CVE-2026-35187
Type (CWE)CWE-22: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVE-2026-35592 is a sibling vulnerability in the same Pyload pyload advisory bundle as CVE-2026-35187. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-35592 matches the primary write-up.

What is different about CVE-2026-35592?

pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev97, the _safe_extractall() function in src/pyload/plugins/extractors/UnTar.py uses os.path.commonprefix() for its path traversal check, which performs character-level string comparison rather than path-level comparison. This allows a specially crafted tar archive to write files outside the intended extraction directory.

Impact is consistent with the bundle: unauthorized file reads or writes through path traversal. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-35592

Apply the patched build per the primary write-up: How to Fix CVE-2026-35187.

For a quick check, confirm the running version of pyload:


# Confirm the installed version via your package manager
dpkg -l | grep -i pyload   # Debian/Ubuntu
rpm -qa | grep -i pyload   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-35592 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-35592?

CVSS rates it 5.3 (Medium). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take pyload offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-35592 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References


*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Pyload pyload advisory bundle. Full procedure at how-to-fix-cve-2026-35187.*