Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-35464

Unsafe Deserialization in pyload-ng (CVE-2026-35464)

Summary

vulnerability in pyload-ng (CVE-2026-35464). Successful exploitation can lead to full system takeover. Exploitable via `POST /api/set_config_value`.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-35464** has been found in pyload-ng. Attackers can target a specific entry point like `POST /api/set_config_value` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: ?/10. What to do: apply the vendor's official patched release. If unsure, ask your IT team or search "pyload-ng CVE-2026-35464" on the vendor's site.
CVE-2026-35464 (pyload-ng) — CWE-502 / Attack vector: remote (network-reachable) / no user interaction Attack surface: POST /api/set_config_value / POST /api/add_package / `ADMIN_ONLY_OPTIONS` / `storage_folder` 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.
❓ What is the problem
**unsafe deserialization** (CWE-502) exists in pyload-ng. Attackers reach the vulnerable code path via `POST /api/set_config_value` without authentication.
📍 Affected scope
pyload-ng — . Attack surface: POST /api/set_config_value / POST /api/add_package / `ADMIN_ONLY_OPTIONS` / `storage_folder`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /api/set_config_value` requests with malformed payloads or SQL meta-characters. Run `grep -r 'pyload-ng' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'pyload-ng' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pyload-ng` を grep し、稼働しているサービス・バージョンを把握する。

  2. 3
    Hunt for indicators of compromise detect 
    grep 'POST /api/set_config_value' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで `POST /api/set_config_value` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 7
    Post-deployment verification verify 
    Replay attack against POST /api/set_config_value on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI pyload-ng
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.5.0b3"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →