Resource exhaustion in Pyload

CVE-2026-48987

pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev101, EventManager in src/pyload/core/managers/event_manager.py appends a Client object to the clients list for each unique uuid submitted to the authenticated getEvents API endpoint, but get_events does not invoke the available clean method to remove inactive clients. An authenticated user can repeatedly submit unique UUID values, causing retained client objects and process memory to grow without bound even after requests stop. The resulting memory exhaustion can trigger an operating-system out-of-memory termination of pyLoad or host-wide instability and denial of service. This issue is fixed in version 0.5.0b3.dev101.

Vulnerability class: DoS (Denial of Service)

Published · last modified .

CVSS v3 metric

CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

EPSS exploit prediction

EPSS: 0.004 (37.9th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 38th percentile — 37.9% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-48987: held from 0.004 to 0.004.

EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: 0.000

Affected products

  • Pyload — versions < 0.5.0b3.dev101

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-48987?
CVE-2026-48987 is a medium-severity vulnerability in Pyload, classified under Uncontrolled Resource Consumption. CVSS score: 6.5/10. Published 2026-09-15.
How severe is CVE-2026-48987?
Medium severity. CVSS v3 base score is 6.5 out of 10.