<?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-10T18:58:33.493637+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/cve-2026-33056</id>
    <title>CVE-2026-33056 — tar-rs: unpack_in can chmod arbitrary directories by following symlinks</title>
    <updated>2026-10-10T18:58:33.527381+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> alexcrichton tar-rs</p>
<p>tar-rs is a tar archive reading/writing library for Rust. In versions 0.4.44 and below, when unpacking a tar archive, the tar crate's unpack_dir function uses fs::metadata() to check whether a path that already exists is a directory. Because fs::metadata() follows symbolic links, a crafted tarball containing a symlink entry followed by a directory entry with the same name causes the crate to treat the symlink target as a valid existing directory — and subsequently apply chmod to it. This allows an attacker to modify the permissions of arbitrary directories outside the extraction root. This issue has been fixed in version 0.4.45.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-33056"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rustsec-2026-0067</id>
    <title>RUSTSEC-2026-0067 — `unpack_in` can chmod arbitrary directories by following symlinks</title>
    <updated>2026-10-10T18:58:33.527446+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: tar</p>
<p>In versions 0.4.44 and below of tar-rs, when unpacking a tar archive, the tar
crate's `unpack_dir` function uses [`fs::metadata()`][fs-metadata] to check
whether a path that already exists is a directory. Because `fs::metadata()`
follows symbolic links, a crafted tarball containing a symlink entry followed
by a directory entry with the same name causes the crate to treat the symlink
target as a valid existing directory — and subsequently apply chmod to it. This
allows an attacker to modify the permissions of arbitrary directories outside
the extraction root.</p>
<p>This issue has been fixed in version 0.4.45.</p>
<p>[fs-metadata]: https://doc.rust-lang.org/std/fs/fn.metadata.html</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rustsec-2026-0067"/>
  </entry>
</feed>
