← Back
CVE-2026-54574
high
CVSS 8.2
Vulnerability in proot-distro (CVE-2026-54574)
Summary
vulnerability in proot-distro (CVE-2026-54574). Confidential information can be exposed externally. Exploitable via ``member.linkname``. Mitigation: upgrade to `5.1.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54574** has been found in proot-distro.
Attackers can target a specific entry point like ``member.linkname`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade proot-distro to **5.1.5** or later.
If unsure, ask your IT team or search "proot-distro CVE-2026-54574" on the vendor's site.
CVE-2026-54574 (proot-distro) — CWE-61 / CVSS v3 8.2
Attack vector: local / unauthenticated
Attack surface: `member.linkname` / `_extract_plain_tar` / `_apply_layer` / `rel_path`
Patched: `5.1.5` — 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-61) exists in proot-distro. Attackers reach the vulnerable code path via ``member.linkname`` without authentication.
📍 Affected scope
proot-distro — . Attack surface: `member.linkname` / `_extract_plain_tar` / `_apply_layer` / `rel_path`.
🔥 Severity
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally
🔧 How to fix
Update to **5.1.5**.
🛡️ 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 'proot-distro' .` 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 'proot-distro' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `proot-distro` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade proot-distro to 5.1.5ステージング環境で 5.1.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
proot-distro
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.5"}]}]