CVE-2026-48987

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-07-09. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

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
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

July 9, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit 1b12dc7f348d (pyload/pyload)

Fix landed in pyload/pyload commit 1b12dc7f348d — awaiting tagged release

https://github.com/pyload/pyload/commit/1b12dc7f348db8c144e0f39215680415e90ca4d2
github Patch Available🟡 PoC Available

Unbounded Memory Growth Leading to DoS and Potential DDoS in EventManager · Advisory · pyload/pyload · GitHub

https://github.com/pyload/pyload/security/advisories/GHSA-c2f9-4mc8-j656

Vendor 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 / EcosystemFixed in / PatchReleasedSource
pippyload-ngghsa

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)
PackageVulnerable rangeFixed inDependents
pyload-ng0.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 10× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 05:37 UTCEG score recompute
  3. 2026-09-18 05:37 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 13:47 UTCGHSA enrichment
  6. 2026-09-15 15:35 UTCEG score recompute
  7. 2026-09-15 15:35 UTCGHSA enrichment
  8. 2026-09-15 14:43 UTCGHSA enrichment
  9. 2026-09-14 06:27 UTCGHSA enrichment
  10. 2026-09-13 08:20 UTCGHSA enrichment
  11. 2026-09-12 03:25 UTCGHSA enrichment
  12. 2026-09-05 22:36 UTCGHSA enrichment
  13. 2026-08-30 06:56 UTCGHSA enrichment
  14. 2026-08-28 02:42 UTCGHSA enrichment
  15. 2026-08-27 02:02 UTCGHSA enrichment
  16. 2026-08-26 03:53 UTCGHSA enrichment
  17. 2026-08-24 20:21 UTCGHSA enrichment
  18. 2026-08-23 18:33 UTCGHSA enrichment
  19. 2026-08-22 20:26 UTCGHSA enrichment
  20. 2026-08-21 22:18 UTCGHSA enrichment
  21. 2026-08-20 23:57 UTCGHSA enrichment
  22. 2026-08-20 01:50 UTCGHSA enrichment
  23. 2026-08-18 20:43 UTCGHSA enrichment
  24. 2026-08-17 16:07 UTCGHSA enrichment
  25. 2026-08-16 17:59 UTCGHSA enrichment
Show 37 more
  1. 2026-08-15 19:50 UTCGHSA enrichment
  2. 2026-08-14 21:41 UTCGHSA enrichment
  3. 2026-08-13 23:34 UTCGHSA enrichment
  4. 2026-08-13 01:25 UTCGHSA enrichment
  5. 2026-08-12 03:18 UTCGHSA enrichment
  6. 2026-08-11 05:10 UTCGHSA enrichment
  7. 2026-08-10 07:02 UTCGHSA enrichment
  8. 2026-08-09 08:54 UTCEG score recompute
  9. 2026-08-09 08:54 UTCGHSA enrichment
  10. 2026-08-08 10:47 UTCGHSA enrichment
  11. 2026-08-07 12:38 UTCGHSA enrichment
  12. 2026-08-06 14:30 UTCGHSA enrichment
  13. 2026-08-05 16:22 UTCGHSA enrichment
  14. 2026-08-04 18:14 UTCGHSA enrichment
  15. 2026-08-03 19:58 UTCGHSA enrichment
  16. 2026-08-02 21:51 UTCGHSA enrichment
  17. 2026-08-01 23:43 UTCGHSA enrichment
  18. 2026-08-01 01:35 UTCGHSA enrichment
  19. 2026-07-31 03:03 UTCEG score recompute
  20. 2026-07-31 03:03 UTCGHSA enrichment
  21. 2026-07-30 04:53 UTCGHSA enrichment
  22. 2026-07-29 06:44 UTCGHSA enrichment
  23. 2026-07-28 08:36 UTCGHSA enrichment
  24. 2026-07-27 10:28 UTCGHSA enrichment
  25. 2026-07-26 12:20 UTCEG score recompute
  26. 2026-07-26 12:20 UTCGHSA enrichment
  27. 2026-07-23 03:18 UTCEG score recompute
  28. 2026-07-16 22:59 UTCGHSA enrichment
  29. 2026-07-16 00:51 UTCGHSA enrichment
  30. 2026-07-15 02:42 UTCGHSA enrichment
  31. 2026-07-14 04:26 UTCGHSA enrichment
  32. 2026-07-13 06:17 UTCGHSA enrichment
  33. 2026-07-12 08:09 UTCGHSA enrichment
  34. 2026-07-11 10:01 UTCGHSA enrichment
  35. 2026-07-10 11:53 UTCGHSA enrichment
  36. 2026-07-09 13:45 UTCEG score recompute
  37. 2026-07-09 13:45 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-48987?
CVE-2026-48987 is a medium vulnerability published on July 9, 2026. pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev101, EventManager in src/pyload/core/managers/eventmanager.py appends a Client object to the clients list for each unique uuid submitted to the authenticated getEvents API endpoint, but getevents does not…
When was CVE-2026-48987 disclosed?
CVE-2026-48987 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48987 actively exploited?
CVE-2026-48987 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.0% of all scored CVEs.
What is the CVSS score of CVE-2026-48987?
CVE-2026-48987 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-48987?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48987, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48987

Explore →

Is Your Infrastructure Affected by CVE-2026-48987?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.