Quick answers
- Is CVE-2026-42312 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42312 being exploited in the wild.
- How severe is CVE-2026-42312?
- Medium severity, with a CVSS score of 6.8, published 11 May 2026.
- Which products and versions are affected?
- pyLoad Next Generation < 0.5.0b3.dev100, <= 0.5.0b3.dev99; pyload-ng (PyPI) <= 0.5.0b3.dev99, ECOSYSTEM:introduced=0,fixed=0.5.0b3.dev100.
- Is there a fix for CVE-2026-42312?
- Yes. pyload-ng (PyPI): upgrade to 0.5.0b3.dev100 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42312 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-42312?
- Check whether you run pyLoad Next Generation or pyload-ng (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- pyload-ng (PyPI): upgrade to 0.5.0b3.dev100 or later
pip install "pyload-ng>=0.5.0b3.dev100"
Technical details
An incorrect authorization vulnerability exists in the `set_config_value()` API method of pyload-ng. The application uses an allowlist, `ADMIN_ONLY_CORE_OPTIONS`, to restrict sensitive configuration changes to administrators; however, the `ssl_verify` option in the `general` category was omitted from this list. An authenticated user with `Perms.SETTINGS` can set `general.ssl_verify` to 'off', which causes the underlying pycurl implementation to set `SSL_VERIFYPEER` and `SSL_VERIFYHOST` to 0. This disables certificate and hostname validation for all subsequent outbound requests, including downloads and update checks. This issue is an incomplete fix for a series of similar allowlist omissions and has been patched in version 0.5.0b3.dev100.
Affected products
- pyload pyload-ng <= 0.5.0b3.dev99
Identifiers
- CVE-2026-42312
- GHSA-ccxc-x975-4hh9
- PYSEC-2026-126
Timeline
- 2026-04-24: disclosed: Vulnerability reported to pyload/pyload
- 2026-05-04: advisory: GitHub Advisory published
- 2026-05-11: other: NVD published CVE-2026-42312