<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-09T10:00:08.119372+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/rustsec-2026-0113</id>
    <title>RUSTSEC-2026-0113 — `unpack_in` can chmod arbitrary directories by following symlinks</title>
    <updated>2026-10-09T10:00:08.121000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: astral-tokio-tar</p>
<p>In versions 0.6.0 and earlier of astral-tokio-tar, the unpack_in API could
inadvertently modify the permissions of external (i.e. non-archive) directories
outside of the archive. An attacker could use this to contrite a tar archive
that maliciously changes directory permissions outside of its intended
hierarchy. This flaw only affects directories; individual file permissions
cannot be modified via it.</p>
<p>See GHSA-j4xf-2g29-59ph for the equivalent flaw in the tar crate.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rustsec-2026-0113"/>
  </entry>
</feed>
