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.
CVE-2026-48987
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.5 from GitHub Security Advisory published 2026-07-09. A secondary CVSS source baseline 6.5; sources differ by 0.0.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
The CVE record names the fixed release — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMmedium confidence
- EG Risk
- 45EG Risk 45/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity65% × 45%The EG Score, 6.5 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: The CVE record names the fixed release. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 36th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
The CVE record names the fixed release. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
July 9, 2026
Last Modified
September 16, 2026
Advisory Details (2)
Auto-updated Sep 15, 2026commit 1b12dc7f348d (pyload/pyload)
Fix landed in pyload/pyload commit 1b12dc7f348d — awaiting tagged release
https://github.com/pyload/pyload/commit/1b12dc7f348db8c144e0f39215680415e90ca4d2Unbounded Memory Growth Leading to DoS and Potential DDoS in EventManager · Advisory · pyload/pyload · GitHub
https://github.com/pyload/pyload/security/advisories/GHSA-c2f9-4mc8-j656Vendor Advisories for CVE-2026-48987(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | pyload-ng | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pyload-ng | 0.5.0a5.dev528 ... 0.5.0b3.dev99 (105 versions) |
| — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 40× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-12 16:00 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-10-12 16:00 UTCEG score recompute
- 2026-10-11 19:43 UTCEG score recompute
- 2026-10-11 16:57 UTCEG score recompute
- 2026-10-11 14:22 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-01 16:03 UTCEG score recompute
- 2026-10-01 16:03 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-28 10:58 UTCEG score recompute
- 2026-09-28 10:58 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
Show 69 moreShow fewer
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-24 11:40 UTCEG score recompute
- 2026-09-24 11:40 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-23 05:59 UTCEG score recompute
- 2026-09-23 05:59 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-18 05:37 UTCEG score recompute
- 2026-09-18 05:37 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-16 13:47 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-09-15 15:35 UTCEG score recompute
- 2026-09-15 15:35 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-09-15 14:43 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-09-14 06:27 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-09-13 08:20 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-09-12 03:25 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-09-05 22:36 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-30 06:56 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-28 02:42 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-27 02:02 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-26 03:53 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-24 20:21 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-23 18:33 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-22 20:26 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-21 22:18 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-20 23:57 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-20 01:50 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-18 20:43 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-17 16:07 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-16 17:59 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-15 19:50 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-14 21:41 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-13 23:34 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-13 01:25 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-12 03:18 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-11 05:10 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-10 07:02 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-09 08:54 UTCEG score recompute
- 2026-08-09 08:54 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-08 10:47 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-07 12:38 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-06 14:30 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-05 16:22 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-04 18:14 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-03 19:58 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-02 21:51 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-01 23:43 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-08-01 01:35 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-31 03:03 UTCEG score recompute
- 2026-07-31 03:03 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-30 04:53 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-29 06:44 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-28 08:36 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-27 10:28 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-26 12:20 UTCEG score recompute
- 2026-07-26 12:20 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-16 22:59 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-16 00:51 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-15 02:42 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-14 04:26 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-13 06:17 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-12 08:09 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-11 10:01 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-10 11:53 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
- 2026-07-09 13:45 UTCEG score recompute
- 2026-07-09 13:45 UTCGHSA enrichmentGHSA-c2f9-4mc8-j656 · GitHub CVSS 6.5
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:pyload-ng
Frequently asked(5)
What is CVE-2026-48987?
When was the CVE record for CVE-2026-48987 published?
Is CVE-2026-48987 actively exploited?
What is the CVSS score of CVE-2026-48987?
How do I remediate CVE-2026-48987?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48987
Is Your Infrastructure Affected by CVE-2026-48987?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.