CVE-2026-48987 json
pyLoad: Unbounded Memory Growth Leading to DoS and Potential DDoS in EventManager
published 4mo ago modified last mo. also EUVD-2026-78594 , GHSA-c2f9-4mc8-j656 , PYSEC-2026-2992
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pyload-ng_project pyload-ng 0.5.0b3.dev101
- pyload pyload 0.5.0b3.dev101
Is CVE-2026-48987 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/pyload/pyload/security/advisories/GHSA-c2f9-4mc8-j656 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pyload-ng | <=0.5.0b3.dev100 |
no fix listed |
Affected products
- pyload pyload
Classification
References
- github.com /pyload/pyload/commit/1b12dc7f348db8c144e0f39215680415e90ca4d2
-
github.com
/pyload/pyload/security/advisories/GHSA-c2f9-4mc8-j656
exploit, web
-
github.com
/pyload/pyload
package
-
pypi.org
/project/pyload-ng
package
-
github.com
/advisories/GHSA-c2f9-4mc8-j656
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-48987
advisory
Sources
- CVE List CVE-2026-48987
- GitHub Advisory GHSA-c2f9-4mc8-j656
- NVD CVE-2026-48987
- OSV PYSEC-2026-2992
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.