CVE-2026-33509: Pyload remote code execution (CVSS 7.5)

Description

pyLoad is a free and open-source download manager written in Python. From version 0.4.0 to before version 0.5.0b3.dev97, the set_config_value() API endpoint allows users with the non-admin SETTINGS permission to modify any configuration option without restriction. The reconnect.script config option controls a file path that is passed directly to subprocess.run() in the thread manager's reconnect logic. A SETTINGS user can set this to any executable file on the system, achieving Remote Code Execution. The only validation in set_config_value() is a hardcoded check for general.storage_folder — all other security-critical settings including reconnect.script are writable without any allowlist or path restriction. This issue has been patched in version 0.5.0b3.dev97.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityHigh

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

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

Affected products

Pyload-ng≥ 0.5.0a5.dev528 < 0.5.0b3.dev97

Pyload≥ 0.4 ≤ 0.4.20

Remediation

Fixed in

Pyload-ng≥ 0.5.0b3.dev97

Patch & vendor advisories

https://github.com/pyload/pyload/security/advisories/GHSA-r7mc-x6x7-cqxx

References

https://github.com/pyload/pyload/security/advisories/GHSA-r7mc-x6x7-cqxxExploitMitigationVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-33509 being actively exploited?

CVE-2026-33509 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.58%.

How severe is CVE-2026-33509?

CVE-2026-33509 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.58% probability of exploitation.

Which products are affected by CVE-2026-33509?

Affected products include Pyload-ng, Pyload.

How do I fix CVE-2026-33509?

Upgrade affected software to a fixed version, for example Pyload-ng 0.5.0b3.dev97 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-33509 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo