CVE-2026-42313 pyload-ng: non-admin SETTINGS users can redirect all outbound traffic through an attacker-controlled proxy
Authenticated non-admin users can configure proxy settings to route all outbound traffic through an attacker-controlled server, enabling data interception.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-42313?
CVE-2026-42313 is a high-severity server-side request forgery vulnerability in pyload, published on 11 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev100, the set_config_value() API method (@permission(Perms.SETTINGS)) in src/pyload/core/api/__init__.py gates security-sensitive options behind a hand-maintained allowlist ADMIN_ONLY_CORE_OPTIONS. The allowlist contains ("proxy", "username") and ("proxy", "password") — which protect the proxy credentials — but it does not include ("proxy", "enabled"), ("proxy", "host"), ("proxy", "port"), or ("proxy", "type"). Any authenticated user with the non-admin SETTINGS permission can enable proxying and point pyload at any host they control. From that point, every outbound download, captcha fetch, update check, and plugin HTTP call is transparently routed through the attacker. This is a direct continuation of the fix family CVE-2026-33509 / CVE-2026-35463 / CVE-2026-35464 / CVE-2026-35586, each of which patched a different missed option in the same allowlist. This vulnerability is fixed in 0.5.0b3.dev100.
Which versions are affected by CVE-2026-42313?
3 open source packages ship an affected version, including pyload-ng. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
pyload-ng PyPI | All versions | 0.5.0b3.dev100 |
pyload-ng PyPI | All versions | 0.5.0b3.dev100 |
pyload-ng PyPI | All versions | 0.5.0b3.dev100 |
Products include Pyload-Ng Project Pyload-Ng.
How do I fix CVE-2026-42313?
Upgrade pyload-ng to 0.5.0b3.dev100 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-42313 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42313 exists.
Other vulnerabilities in pyload
- CVE-2025-54802 pyLoad CNL Blueprint is vulnerable to Path Traversal through `dlc_path` leading to Remote Code Execution (RCE)
- CVE-2024-22416 Cross-Site Request Forgery on any API call in pyLoad may lead to admin privilege escalation
- CVE-2023-0488 Cross-site Scripting (XSS) - Stored in pyload/pyload
- CVE-2026-35459 pyLoad has SSRF fix bypass via HTTP redirect
- CVE-2026-35463 pyLoad has Improper Neutralization of Special Elements used in an OS Command
Sources
Also known as GHSA-pg67-9wjv-mr85, PYSEC-2026-127.