<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T19:27:18.658694+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-342496</id>
    <title>EUVD-2026-342496</title>
    <updated>2026-10-02T19:27:18.857273+00:00</updated>
    <content>EUVD-2026-342496</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-342496"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54574</id>
    <title>fkie_cve-2026-54574</title>
    <updated>2026-10-02T19:27:18.857374+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>proot-distro is a utility for managing proot containers. Prior to version 5.1.5, proot-distro install extracted plain tarball root filesystems through _extract_plain_tar() in proot_distro/commands/install.py and Docker layers through _apply_layer() in proot_distro/helpers/docker.py without validating archive-controlled symlink targets in member.linkname, allowing a malicious archive to plant an absolute host-path symlink and write files through it onto the host filesystem. This issue is fixed in version 5.1.5.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-54574"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9xq3-3fqg-4vg7</id>
    <title>GHSA-9xq3-3fqg-4vg7 — `proot-distro install` has a Symlink Escape (Arbitrary Host File Write) via Malicious Tar Archive</title>
    <updated>2026-10-02T19:27:18.857450+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: proot-distro</p>
<p>**Repository:** `termux/proot-distro`  
**Component:** `proot_distro/commands/install.py` → `_extract_plain_tar()`; also `helpers/docker.py` → `_apply_layer()`</p>
<p>---</p>
<p>## Affected Versions</p>
<p>| Component     | Version                      |
|---------------|------------------------------|
| proot-distro  | 5.0.2 (confirmed vulnerable) |
| Termux app    | 0.119.0-beta.3               |
| Device / ABI  | Samsung Galaxy A23 / aarch64 |
| Python (host) | 3.13                         |</p>
<p>---</p>
<p>## Vulnerability Description</p>
<p>`proot-distro install` extracts a plain tarball rootfs by calling `_extract_plain_tar()` in
`proot_distro/commands/install.py`. This function correctly rejects tar member **names**
containing `..` components, but applies **no equivalent check on symlink targets**
(`member.linkname`). A tar archive can therefore:</p>
<p>1. Plant a symlink inside the rootfs whose target is an **absolute host path**
   (e.g. `/data/data/com.termux/files/home`).
2. Write a subsequent regular-file member whose path traverses through that symlink name.</p>
<p>Python's `open()` follows the symlink, writing the file **on the host filesystem** at the
privilege level of the Termux process — entirely during `proot-distro install`, before the
container is ever run.</p>
<p>The same `_extract_plain_tar` function is reachable via `proot-distro reset`, and the
equivalent `_apply_layer` in `helpers/docker.py` contains the same flaw.</p>
<p>---</p>
<p>## Vulnerable Code</p>
<p>**`proot_distro/commands/install.py`**, `_extract_plain_…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9xq3-3fqg-4vg7"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-3608</id>
    <title>PYSEC-2026-3608 — `proot-distro install` has a Symlink Escape (Arbitrary Host File Write) via Malicious Tar Archive</title>
    <updated>2026-10-02T19:27:18.857624+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: proot-distro</p>
<p>**Repository:** `termux/proot-distro`  
**Component:** `proot_distro/commands/install.py` → `_extract_plain_tar()`; also `helpers/docker.py` → `_apply_layer()`</p>
<p>---</p>
<p>## Affected Versions</p>
<p>| Component     | Version                      |
|---------------|------------------------------|
| proot-distro  | 5.0.2 (confirmed vulnerable) |
| Termux app    | 0.119.0-beta.3               |
| Device / ABI  | Samsung Galaxy A23 / aarch64 |
| Python (host) | 3.13                         |</p>
<p>---</p>
<p>## Vulnerability Description</p>
<p>`proot-distro install` extracts a plain tarball rootfs by calling `_extract_plain_tar()` in
`proot_distro/commands/install.py`. This function correctly rejects tar member **names**
containing `..` components, but applies **no equivalent check on symlink targets**
(`member.linkname`). A tar archive can therefore:</p>
<p>1. Plant a symlink inside the rootfs whose target is an **absolute host path**
   (e.g. `/data/data/com.termux/files/home`).
2. Write a subsequent regular-file member whose path traverses through that symlink name.</p>
<p>Python's `open()` follows the symlink, writing the file **on the host filesystem** at the
privilege level of the Termux process — entirely during `proot-distro install`, before the
container is ever run.</p>
<p>The same `_extract_plain_tar` function is reachable via `proot-distro reset`, and the
equivalent `_apply_layer` in `helpers/docker.py` contains the same flaw.</p>
<p>---</p>
<p>## Vulnerable Code</p>
<p>**`proot_distro/commands/install.py`**, `_extract_plain_…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-3608"/>
  </entry>
</feed>
