← Back
CVE-2026-42314
medium
CVSS 6.5
Path Traversal in pyload-ng (CVE-2026-42314)
Summary
path traversal in pyload-ng (CVE-2026-42314). Data can be tampered with by attackers. Mitigation: upgrade to `0.5.0b3.dev100` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42314** has been found in pyload-ng.
Data can be tampered with by attackers. CVSS score: 6.5/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-42314" on the vendor's site.
CVE-2026-42314 (pyload-ng) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
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
**Path traversal** (CWE-22) exists in pyload-ng.
📍 Affected scope
pyload-ng — .
🔥 Severity
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers
🔧 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pyload-ng to 0.5.0b3.dev100ステージング環境で 0.5.0b3.dev100 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
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"}]}]