CVE-2026-54574

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

proot-distro is a utility for managing proot containers. Prior to version 5.1.5, proot-distro install extracted plain tarball root filesystems through _extract_plain_tar() in proot_distro/commands/install.py and Docker layers through _apply_layer() in proot_distro/helpers/docker.py without validating archive-controlled symlink targets in member.linkname, allowing a malicious archive to plant an absolute host-path symlink and write files through it onto the host filesystem. This issue is fixed in version 5.1.5.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
53(Track*)
EG Risk 53/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (3)

Auto-updated Jul 29, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github_release Patch Available

Version 5.1.5

Patch available: termux/proot-distro v5.1.5

https://github.com/termux/proot-distro/releases/tag/v5.1.5
github_commit Patch Available

commit a96d7a9667f3 (termux/proot-distro)

Patch available: termux/proot-distro v5.1.5 (contains commit a96d7a9667f3)

https://github.com/termux/proot-distro/commit/a96d7a9667f38e45d812614852ee3915d1c0ae45
github Patch Available🟡 PoC Available

Symlink Escape (Arbitrary Host File Write) in `proot-distro install` via Malicious Tar Archive · Advisory · termux/proot-distro · GitHub

https://github.com/termux/proot-distro/security/advisories/GHSA-9xq3-3fqg-4vg7

Vendor Advisories for CVE-2026-54574(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
proot-distro5.0.0 ... 5.1.4 (13 versions)5.1.5

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 19:16 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 17:54 UTCEG score recompute
  4. 2026-08-23 03:00 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 01:42 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 00:26 UTCEG score recompute
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 23:07 UTCEG score recompute
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 21:45 UTCEG score recompute
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 19:54 UTCEG score recompute
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 16:22 UTCEG score recompute
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 03:45 UTCEG score recompute
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 02:30 UTCEG score recompute
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 01:16 UTCEG score recompute
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 00:02 UTCEG score recompute
  25. 2026-08-12 13:51 UTCEPSS rescore
Show 28 more
  1. 2026-08-11 22:47 UTCEG score recompute
  2. 2026-08-11 10:10 UTCEG score recompute
  3. 2026-08-11 00:00 UTCEPSS rescore
  4. 2026-08-09 20:18 UTCEG score recompute
  5. 2026-08-09 13:46 UTCEPSS rescore
  6. 2026-08-08 19:04 UTCEG score recompute
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-06 16:35 UTCEG score recompute
  9. 2026-08-06 13:47 UTCEPSS rescore
  10. 2026-08-06 03:56 UTCEG score recompute
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-05 02:42 UTCEG score recompute
  13. 2026-08-04 15:10 UTCEPSS rescore
  14. 2026-08-04 14:05 UTCEG score recompute
  15. 2026-08-04 10:39 UTCEPSS rescore
  16. 2026-08-03 12:50 UTCEG score recompute
  17. 2026-08-03 10:36 UTCEPSS rescore
  18. 2026-08-02 11:24 UTCEG score recompute
  19. 2026-08-02 02:27 UTCEPSS rescore
  20. 2026-08-01 10:09 UTCEG score recompute
  21. 2026-08-01 04:16 UTCEPSS rescore
  22. 2026-07-30 20:13 UTCEG score recompute
  23. 2026-07-30 16:28 UTCEPSS rescore
  24. 2026-07-29 20:22 UTCEG score recompute
  25. 2026-07-29 20:01 UTCEG score recompute
  26. 2026-07-29 17:26 UTCEG score recompute
  27. 2026-07-29 16:38 UTCEG score recompute
  28. 2026-07-29 16:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54574?
CVE-2026-54574 is a high vulnerability published on July 29, 2026. proot-distro is a utility for managing proot containers. Prior to version 5.1.5, proot-distro install extracted plain tarball root filesystems through extractplaintar() in prootdistro/commands/install.py and Docker layers through applylayer() in proot_distro/helpers/docker.py without validating…
When was CVE-2026-54574 disclosed?
CVE-2026-54574 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54574 actively exploited?
CVE-2026-54574 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.0% of all scored CVEs.
What is the CVSS score of CVE-2026-54574?
CVE-2026-54574 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-54574?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54574, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54574

Explore →

Is Your Infrastructure Affected by CVE-2026-54574?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.