User-assisted cross-container file read and write via hardlinks
Published Jul 29, 2026 · Updated Jul 29, 2026
Improper container isolation in Termux PRoot-Distro before 5.1.6 allows attackers to read and write cross-container files via crafted archives. The restore command resolves a hardlink source from the archive linkname and copies it without confirming that its source container matches the destination container. Exploitation requires a user to restore the archive; copying remains inside the containers directory but can disclose secrets or inject attacker-controlled files.
Summary
What happened
Improper container isolation in Termux PRoot-Distro before 5.1.6 allows attackers to read and write cross-container files via crafted archives. The restore command resolves a hardlink source from the archive linkname and copies it without confirming that its source container matches the destination container. Exploitation requires a user to restore the archive; copying remains inside the containers directory but can disclose secrets or inject attacker-controlled files.
The record
- CVE
- CVE-2026-54727
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- Termux
- Product
- PRoot-Distro
- Classifications
- CWE-668, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2026CVE publishedPublication date reported by the CVE source.
- Jul 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.1.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Cross-container disclosure and file-injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo