Categories
CVE-2026-42313 high CVSS 8.3

Vulnerability in pyload-ng (CVE-2026-42313)

Summary

Vulnerability in pyload-ng (CVE-2026-42313). Confidential information can be exposed externally. Exploitable via ADMIN_ONLY_CORE_OPTIONS. Mitigation: upgrade to 0.5.0b3.dev100 or later.

Original description

The description as published by the source.

Summary

The set_config_value() API method (@permission(Perms.SETTINGS)) in src/pyload/core/api/__init__.py gates security-sensitive options behind a hand-maintained allowlist ADMIN_ONLY_CORE_OPTIONS. The allowlist contains ("proxy", "username") and ("proxy", "password") — which protect the proxy credentials — but it does not include ("proxy", "enabled"), ("proxy", "host"), ("proxy", "port"), or ("proxy", "type"). Any authenticated user with the non-admin SETTINGS permission can enable proxying and point pyload at any host they control. From that point, every outbound download, captcha fetch, update check, and plugin HTTP call is transparently routed through the attacker.

Gating only the proxy credentials is ineffective: the attacker is the proxy endpoint, so they do not need pyload's proxy-auth secret. proxy.username / proxy.password were designed so an admin could authenticate to a trusted corporate proxy; they do not help when the non-admin attacker is free to choose the proxy itself.

This is a direct continuation of the fix family CVE-2026-33509 / CVE-2026-35463 / CVE-2026-35464 / CVE-2026-35586, each of which patched a different missed option in the same allowlist. CVE-2026-35586 in particular bundled three related SSL-cert options into one advisory on the same rationale applied here — the four proxy.* fields are jointly required to weaponize the miss and are patched together.

Details

Writer — `src/pyload/core/api/init.…

Source: NIST National Vulnerability Database 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-42313 has been found in pyload-ng.
Attackers can target a specific entry point like ADMIN_ONLY_CORE_OPTIONS over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.3/10.
What to do: upgrade pyload-ng to 0.5.0b3.dev100 or later.
If unsure, ask your IT team or search "pyload-ng CVE-2026-42313" on the vendor's site.

CVE-2026-42313 (pyload-ng) — CWE-441 / CVSS v3 8.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ADMIN_ONLY_CORE_OPTIONS / SETTINGS / proxy.username / proxy.password
Patched: 0.5.0b3.dev100 — 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.

❓ What is the problem

A vulnerability (CWE-441) exists in pyload-ng. Attackers reach the vulnerable code path via ADMIN_ONLY_CORE_OPTIONS.

📍 Affected scope

Check the vendor advisory for the affected versions of pyload-ng. Attack surface: ADMIN_ONLY_CORE_OPTIONS / SETTINGS / proxy.username / proxy.password.

🔥 Severity

Severity: High (CVSS 8.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.5.0b3.dev100.

🛡️ 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 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

  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. 2
    Apply patch patch
    Upgrade pyload-ng to 0.5.0b3.dev100

    ステージング環境で 0.5.0b3.dev100 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

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

Affected packages

pip pyload-ng
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.0b3.dev100"}]}]
PyPI pyload-ng
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.0b3.dev100"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details