pyLoad: Lack of Input Size Validation Leads to Denial of Service (DoS) and Process Termination

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-48484: 0.37% estimated exploitation activity in the next 30 days; percentile 31.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Description: The API rpc function in apiblueprint.py handles multipart/form-data uploads by reading the whole content of the uploaded file into memory with file.read(). This occurs before the data is sent to the underlying function. Since there is no size limit set at this point, a large file upload can exhaust the server's available memory which led to process termination. VulnerableCode & Path: https://github.com/pyload/pyload/blob/8e447958b8a66c5899775e725a8b90bce6643004/src/pyload/webui/app/blueprints/apiblueprint.py#L73 Steps to Reproduce: 1. Log in to pyLoad (or use an API key, here i used api to communicate). 2. Prepare a large file (e.g., 10GB) . 3. Send a multipart request to an API function that accepts a file, such as checkonlinestatuscontainer: 4. Monitor the server's memory usage. The process will attempt to allocate memory for the entire file and last the process will be killed by the kernel. <img width="1902" height="610" alt="dos-process-kill-poc"…

Published by the source

9 Oct 2026, 16:26 UTC

Last modified by the source

9 Oct 2026, 16:26 UTC

Source last checked

26 Oct 2026, 13:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vq8p-m3wm-gv5f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-48484

Advisory: pyLoad: Lack of Input Size Validation Leads to Denial of Service (DoS) and Process Termination
IDs: CVE-2026-48484, GHSA-vq8p-m3wm-gv5f
Record: https://patchnext.com/advisories/cve-2026-48484 (revision 1, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pyload-ng 0.5.0b3.dev101. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pyload-ng: affected < 0.5.0b3.dev101; fixed in 0.5.0b3.dev101

## Suggested inspection (read-only)
- `python -m pip show pyload-ng`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pyload-ng.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vq8p-m3wm-gv5f (GitHub-reviewed advisory GHSA-vq8p-m3wm-gv5f lists affected ranges: PyPI pyload-ng >=0 <0.5.0b3.dev101)

Commands are suggestions: review each one before running it.