Vulnerability in proot-distro (CVE-2026-54727)
Summary
Vulnerability in proot-distro (CVE-2026-54727). Confidential information can be exposed externally. Exploitable via restore. Mitigation: upgrade to 5.1.6 or later.
Original description
The description as published by the source.
proot-distro is a utility for managing proot containers. Prior to version 5.1.6, proot-distro restore accepted hardlink entries whose linkname referenced another installed container and did not verify that the hardlink source container matched the destination container being restored, allowing a crafted restore archive to copy files between otherwise isolated containers. This issue is fixed in version 5.1.6.
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-54727 has been found in proot-distro.
Attackers can target a specific entry point like restore 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.6 or later.
If unsure, ask your IT team or search "proot-distro CVE-2026-54727" on the vendor's site.
CVE-2026-54727 (proot-distro) — CWE-668 / CVSS v3 8.2
Attack vector: local / unauthenticated
Attack surface: restore / linkname / ATTACKER_DATA
Patched: 5.1.6 — 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-668) exists in proot-distro. Attackers reach the vulnerable code path via restore without authentication.
Check the vendor advisory for the affected versions of proot-distro. Attack surface: restore / linkname / ATTACKER_DATA.
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.
Update to 5.1.6.
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 'proot-distro' . 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 'proot-distro' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
proot-distroを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade proot-distro to 5.1.6ステージング環境で 5.1.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- web github.com