Vulnerability in pyload-ng (CVE-2026-48484)
Summary
Vulnerability in pyload-ng (CVE-2026-48484). Risk of unauthorized operations or information disclosure. Exploitable via rpc. Mitigation: upgrade to 0.5.0b3.dev101 or later.
Original description
The description as published by the source.
Description:
The API rpc function in api_blueprint.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:
Steps to Reproduce:
- Log in to pyLoad (or use an API key, here i used api to communicate).
- Prepare a large file (e.g., 10GB) .
truncate -s 10G large_file.bin
- Send a multipart request to an API function that accepts a file, such as
check_online_status_container:
curl -X POST "http://localhost:8000/api/rpc" \
-H "X-API-Key: YOUR_API_KEY" \
-F "func=check_online_status_container" \
-F "container=@large_file.bin"
- 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.
Impact
- Denial of Service (DoS): The pyLoad process will be killed by the Operating System's Out-Of-Memory (OOM) killer, or the entire system may become unresponsive due to swap thrashing or memory exhaustion.
- Service Instability: Any active downloads or tasks will be interrupted.
Mitigations
- **Implement…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48484 has been found in pyload-ng.
Attackers can target a specific entry point like rpc over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade pyload-ng to 0.5.0b3.dev101 or later.
If unsure, ask your IT team or search "pyload-ng CVE-2026-48484" on the vendor's site.
CVE-2026-48484 (pyload-ng) — CWE-20 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: rpc / api_blueprint.py / check_online_status_container / client_max_body_size
Patched: 0.5.0b3.dev101 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in pyload-ng. Attackers reach the vulnerable code path via rpc.
Check the vendor advisory for the affected versions of pyload-ng. Attack surface: rpc / api_blueprint.py / check_online_status_container / client_max_body_size.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.5.0b3.dev101.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pyload-ng' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pyload-ng' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pyload-ngを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pyload-ng to 0.5.0b3.dev101ステージング環境で 0.5.0b3.dev101 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。