Loading story…
A high-severity vulnerability tracked as CVE-2026-54727 affected proot-distro versions earlier than 5.1.6, allowing a crafted restore archive to bypass container isolation in Termux. The flaw was in the restore process for TAR hardlinks: the tool verified that links stayed within the broader containers directory, but did not ensure the hardlink source belonged to the same container being restored. As a result, a malicious archive could create links into another installed container's rootfs owned by the same user and copy or expose files across otherwise isolated environments.
Reports also described a second weakness in names.py, where use of the Python regex anchor $ instead of \Z allowed trailing newline characters in container names, creating potential command-injection or filesystem-confusion risks. The issue was classified as CWE-668 with CVSS v3.1 AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N, and maintainers fixed it in proot-distro 5.1.6 by rejecting hardlinks whose source container does not match the restore target and tightening container-name validation.
See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
A vulnerability in proot-distro's restore functionality allowed crafted archives with hardlinks to copy files between otherwise isolated containers. The issue was fixed in proot-distro version 5.1.6, which added checks to skip hardlinks when the source container does not match the restore target and tightened container-name validation.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvereports.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A high-severity flaw tracked as **CVE-2026-54574** affects **Termux `proot-distro`** versions earlier than **5.1.5**, allowing a malicious archive to escape the intended extraction directory and write files to arbitrary locations on the host filesystem. The bug lies in `proot-distro`'s handling of plain tarball root filesystems and Docker layers during operations such as **`proot-distro install`** and **`proot-distro restore`**, where archive-controlled symbolic links were not safely validated before subsequent files were extracted through them. The vulnerability arises because lexical path traversal checks did not account for filesystem state changes after a symlink was created, enabling an attacker to craft an archive that first creates a symlink to an absolute host path and then writes a later file through that link. Reported impact includes possible writes to sensitive files such as `/etc/shadow` or files in a Termux home directory, with the issue classified as **CWE-61** and scored **CVSS 7.1** (`AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`). The issue was fixed in **`proot-distro` 5.1.5**, including a safer extraction approach using `_safe_resolve()` in `proot_distro/helpers/tar_extract.py`.
Jul 30, 2026
A security flaw in **Tecnativa `docker-socket-proxy`** allows unintended read access to container data when the proxy is configured with `CONTAINERS=1`, even if `POST=0` is set. Public reports and a proof of concept show that the proxy's HAProxy rules broadly permit the Docker API `/containers/*` namespace, enabling an attacker with access behind the proxy to list containers and reach sensitive GET endpoints that were not meant to be exposed. The exposed endpoints reportedly include `/archive`, `/export`, `/logs`, and `/top`, which can be used to read arbitrary files from containers, export full container filesystems, inspect process arguments, and retrieve logs. An open issue states there is no built-in mitigation short of manually editing the HAProxy configuration, while a linked pull request proposes restricting filesystem-related exposure through more granular controls such as `ALLOW_ARCHIVE`, `ALLOW_EXPORT`, and `ALLOW_LOGS` and corresponding HAProxy configuration changes.
Aug 23, 2026
Dokploy disclosed and patched **CVE-2026-72878**, an OS command injection vulnerability in its backup and restore pipeline that allows an authenticated admin or owner to execute arbitrary commands on the host running the self-hosted PaaS. The flaw affects versions prior to `0.29.13` and arises from user-controlled database fields being interpolated directly into `bash` and `sh` command strings executed through `child_process.exec()`, giving attackers a path to host-level code execution rather than confinement inside application containers. The remediation in Dokploy `0.29.13` hardens multiple backup and restore paths by escaping shell arguments with the `shell-quote` library. The patch replaces unsafe interpolation across workflows involving `rclone`, `gunzip`, `unzip`, and restore operations for Compose, LibSQL, MariaDB, MongoDB, MySQL, PostgreSQL, and web server backups, while also protecting S3-related parameters including bucket paths, backup filenames, temporary directories, access keys, secret keys, region, endpoint, and provider.
Aug 11, 2026