Skip to main content
VulnerabilityPublished

CVE-2026-54727: termux proot-distro · Resource Exposure

Affects termux proot-distroSource CVE Database V5

0

Not known to be exploited · CVSS 8.2 High : upgrade to 5.1.6 soon.

Data as of 27 Oct 2026, 05:11 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.1.6
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade proot-distro and termux/proot-distro to 5.1.6.

Affected software

ProductAffectedFixed in
termuxproot-distroAffected
  • <5.1.6
Fixed in
  • 5.1.6
GitHubtermux/proot-distropkg:github/termux/proot-distroOther threatsAffected
  • <5.1.6
Fixed in
  • 5.1.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in proot-distro version 5.1.6. Users should upgrade to version 5.1.6 or later to remediate this vulnerability. No other mitigation or temporary workaround is indicated.

Description

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.

References

Community reviews

Loading reviews…