Quick answers
- Is CVE-2026-48987 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48987 being exploited in the wild.
- How severe is CVE-2026-48987?
- Medium severity, with a CVSS score of 6.5, published 15 September 2026.
- Which products and versions are affected?
- pyload-ng (PyPI) <= 0.5.0b3.dev100, ECOSYSTEM:introduced=0,last_affected=0.5.0b3.dev100.
- Is there a fix for CVE-2026-48987?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-48987 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48987?
- Check whether you run 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.
Technical details
A resource exhaustion vulnerability exists in the pyLoad EventManager module due to uncontrolled resource consumption (CWE-400). The `get_events` API endpoint creates a new `Client` instance for every unique `uuid` provided in a request and appends it to a global list. Although a `clean()` method exists to remove inactive clients, it is never invoked by the application core. An authenticated attacker can flood the `getEvents` endpoint with unique UUIDs, leading to memory exhaustion and an Out-of-Memory (OOM) kill. As of the advisory date, no patched version is specified, but mitigations include manually invoking `clean()` or implementing rate limiting.
Affected products
- pyload pyload-ng <= 0.5.0b3.dev100
Identifiers
- CVE-2026-48987
- GHSA-c2f9-4mc8-j656
- PYSEC-2026-2992
Timeline
- 2026-07-08: disclosed: Advisory published to pyload/pyload repository
- 2026-07-09: advisory: GitHub Advisory GHSA-c2f9-4mc8-j656 published