<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 03:27:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-54727 — proot-distro has a Container Isolation Bypass via Crafted Restore Archive</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-54727</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; termux proot-distro&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; termux proot-distro&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-54727</guid>
    </item>
    <item>
      <title>GHSA-7h3g-4w2f-fj2f — proot-distro has a Container Isolation Bypass via Crafted Restore Archive</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7h3g-4w2f-fj2f</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: proot-distro&lt;/p&gt;
&lt;p&gt;## Affected Component&lt;/p&gt;
&lt;p&gt;- **Package:** proot-distro
- **Affected command:** `restore`
- **Attack surface:** Host-side Termux CLI processing a user-supplied backup archive
- **Vulnerability type:** Container Isolation Bypass / Cross-Container Read and Write&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Affected Versions&lt;/p&gt;
&lt;p&gt;| Component | Version |
|---|---|
| proot-distro | 5.1.5 (confirmed affected) |
| Test distro | Alpine Linux |
| Architecture | aarch64 |
| Device | Samsung Galaxy A23 |
| Package source | https://packages-cf.termux.dev/apt/termux-main stable/main aarch64 |&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When restoring a crafted backup archive, `proot-distro restore` accepts hardlink entries whose source path references a different installed container.&lt;/p&gt;
&lt;p&gt;The restore logic resolves the hardlink source from the archive&amp;#39;s `linkname` field and copies the referenced file into the container identified by the archive entry.&lt;/p&gt;
&lt;p&gt;Although path traversal protections correctly keep the source path inside the proot-distro containers directory, no validation ensures that the hardlink source container matches the destination container.&lt;/p&gt;
&lt;p&gt;As a result, a malicious backup archive can copy files between otherwise isolated containers, enabling both cross-container disclosure and cross-container file injection.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Proof of Concept #1 — Cross-Container File Disclosure&lt;/p&gt;
&lt;p&gt;All testing was performed using self-owned containers and harmless marker data only.&lt;/p&gt;
&lt;p&gt;### Step 1 — Create a victim container and marker file&lt;/p&gt;
&lt;p&gt;```bash
proot-distro install alpine -…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: proot-distro&lt;/p&gt;
&lt;p&gt;## Affected Component&lt;/p&gt;
&lt;p&gt;- **Package:** proot-distro
- **Affected command:** `restore`
- **Attack surface:** Host-side Termux CLI processing a user-supplied backup archive
- **Vulnerability type:** Container Isolation Bypass / Cross-Container Read and Write&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Affected Versions&lt;/p&gt;
&lt;p&gt;| Component | Version |
|---|---|
| proot-distro | 5.1.5 (confirmed affected) |
| Test distro | Alpine Linux |
| Architecture | aarch64 |
| Device | Samsung Galaxy A23 |
| Package source | https://packages-cf.termux.dev/apt/termux-main stable/main aarch64 |&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When restoring a crafted backup archive, `proot-distro restore` accepts hardlink entries whose source path references a different installed container.&lt;/p&gt;
&lt;p&gt;The restore logic resolves the hardlink source from the archive&amp;#39;s `linkname` field and copies the referenced file into the container identified by the archive entry.&lt;/p&gt;
&lt;p&gt;Although path traversal protections correctly keep the source path inside the proot-distro containers directory, no validation ensures that the hardlink source container matches the destination container.&lt;/p&gt;
&lt;p&gt;As a result, a malicious backup archive can copy files between otherwise isolated containers, enabling both cross-container disclosure and cross-container file injection.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Proof of Concept #1 — Cross-Container File Disclosure&lt;/p&gt;
&lt;p&gt;All testing was performed using self-owned containers and harmless marker data only.&lt;/p&gt;
&lt;p&gt;### Step 1 — Create a victim container and marker file&lt;/p&gt;
&lt;p&gt;```bash
proot-distro install alpine -…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7h3g-4w2f-fj2f</guid>
    </item>
  </channel>
</rss>
