Unrated

pyLoad EventManager getEvents Unbounded Memory Consumption DoS

IdentifiersCVE-2026-48987CWE-770

CVE-2026-48987 is an unbounded memory growth vulnerability in pyLoad's EventManager component affecting the getEvents API path. The flaw arises because repeated requests using distinct UUID values cause the application to create and retain new Client instances without adequate cleanup or limits. Because inactive clients are not purged during get_events processing, an authenticated attacker can continuously expand server-side state and drive memory usage upward. This can exhaust available memory and destabilize or terminate the pyLoad process, resulting in denial of service.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated attacker to trigger uncontrolled memory consumption in the pyLoad service. Sustained abuse can cause the process to be terminated by the operating system due to out-of-memory conditions or can degrade host stability, producing application-level denial of service and potentially broader service disruption on the affected system.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the affected API to trusted users only, and apply rate limiting, quotas, or other request-control mechanisms to the getEvents endpoint. As an interim defensive measure, ensure inactive EventManager clients are cleaned regularly, including by invoking clean() at the start of get_events. Operational monitoring for abnormal memory growth and aggressive recycling of the service can reduce impact until a permanent fix is deployed.

Remediation

Patch, then assume compromise.

Upgrade to a vendor-fixed release when available. If source-level remediation is required before an official release, modify the get_events code path so that EventManager.clean() is invoked before processing or registering clients, ensuring inactive client objects are purged. In addition, enforce limits on client creation and apply request throttling or equivalent controls to the getEvents API to prevent abuse through repeated unique UUID submissions.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

PyloadPyload-Ngapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity