CVE-2026-54574 is a symlink handling vulnerability in proot-distro, a utility for managing proot containers. Versions prior to 5.1.5 improperly handled archive extraction during proot-distro install. Specifically, _extract_plain_tar() in proot_distro/commands/install.py and _apply_layer() in proot_distro/helpers/docker.py processed plain tarball root filesystems and Docker layers without validating archive-controlled symlink targets stored in member.linkname. A malicious archive can therefore create an absolute symlink pointing outside the intended root filesystem extraction directory and then place subsequent files through that symlink onto the host filesystem. This results in a symlink escape from the container rootfs extraction context into host-accessible paths writable by the Termux process.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
rootfs_dir during both plain tarball extraction and Docker layer application. Ensure all deployments use the fixed release for any installation or reset workflows involving root filesystem archives.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.