Skip to content
Infrastructure

CVE-2026-54727

8.2
High
EPSS 0.12%Patch availableJul 30, 2026

proot-distro restore hardlink flaw allows cross-container file copy/escape

common questions

Is CVE-2026-54727 being exploited?

Not confirmed. CVE-2026-54727 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.

How severe is CVE-2026-54727?

CVE-2026-54727 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-54727?

Yes. A fix has been recorded for CVE-2026-54727. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-54727 affect?

CVE-2026-54727 affects proot-distro < 5.1.6, proot-based containers on Linux, systems restoring untrusted archives. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-54727?

Upgrade proot-distro to 5.1.6 and validate restore archives

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
proot-distro < 5.1.6proot-based containers on Linuxsystems restoring untrusted archives
impact

Crafted restore archives can copy/overwrite files across containers, enabling data theft, container escape, or injected files that may lead to code execution.

action required

Patch when possible

affected versions
termux proot-distro
  • affected< 5.1.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free