<?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>Fri, 02 Oct 2026 18:37:28 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-08152</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-08152</link>
      <description>bdu:2026-08152</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-08152</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-5223</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-5223</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: rust, Alpaquita:25: rust, Alpaquita:stream: rust&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: rust, Alpaquita:25: rust, Alpaquita:stream: rust&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-5223</guid>
    </item>
    <item>
      <title>EUVD-2026-322250</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-322250</link>
      <description>EUVD-2026-322250</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-322250</guid>
    </item>
    <item>
      <title>fkie_cve-2026-5223</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-5223</link>
      <description>&lt;p&gt;Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a malicious crate to override the source code of another crate from the same registry. The severity of the vulnerability is **medium** for users of third-party registries. Users of crates.io are **not affected**, as crates.io forbids uploading crates containing any symlink.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a malicious crate to override the source code of another crate from the same registry. The severity of the vulnerability is **medium** for users of third-party registries. Users of crates.io are **not affected**, as crates.io forbids uploading crates containing any symlink.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-5223</guid>
    </item>
    <item>
      <title>GHSA-jq42-7mfv-hm57 — Cargo crates in third party registries can override the cached source of other crates</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jq42-7mfv-hm57</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: cargo&lt;/p&gt;
&lt;p&gt;The Rust Security Response Team was notified that Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a malicious crate to override the source code of another crate from the same registry.&lt;/p&gt;
&lt;p&gt;This vulnerability is tracked as CVE-2026-5223. The severity of the vulnerability is **medium** for users of third-party registries. Users of crates.io are **not affected**, as crates.io forbids uploading crates containing any symlink.&lt;/p&gt;
&lt;p&gt;## Overview&lt;/p&gt;
&lt;p&gt;When building a crate, Cargo extracts its source code in a local cache (stored within `~/.cargo`), reusing it for any future build. Cargo includes protections to prevent any file from being extracted outside of the crate&amp;#39;s own cache directory.&lt;/p&gt;
&lt;p&gt;It was discovered that it&amp;#39;s possible to craft a malicious tarball able to extract files one level below the crate&amp;#39;s own cache directory. With the way the cache is structured, that allowed the malicious crate to override the cache of other crates belonging to the same registry.&lt;/p&gt;
&lt;p&gt;## Mitigations&lt;/p&gt;
&lt;p&gt;Rust 1.96.0, to be released on May 28th, 2026, will update Cargo to reject extracting *any* symlink within crate tarballs, regardless of whether they come from crates.io (which already forbids them) or third-party registries. Note that Cargo never added symlinks when running `cargo package` or `cargo publish`, so the impact of this should be minimal.&lt;/p&gt;
&lt;p&gt;Users who are not able to upgrade to the most recent Rust version are recommended to audit the contents of t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: cargo&lt;/p&gt;
&lt;p&gt;The Rust Security Response Team was notified that Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a malicious crate to override the source code of another crate from the same registry.&lt;/p&gt;
&lt;p&gt;This vulnerability is tracked as CVE-2026-5223. The severity of the vulnerability is **medium** for users of third-party registries. Users of crates.io are **not affected**, as crates.io forbids uploading crates containing any symlink.&lt;/p&gt;
&lt;p&gt;## Overview&lt;/p&gt;
&lt;p&gt;When building a crate, Cargo extracts its source code in a local cache (stored within `~/.cargo`), reusing it for any future build. Cargo includes protections to prevent any file from being extracted outside of the crate&amp;#39;s own cache directory.&lt;/p&gt;
&lt;p&gt;It was discovered that it&amp;#39;s possible to craft a malicious tarball able to extract files one level below the crate&amp;#39;s own cache directory. With the way the cache is structured, that allowed the malicious crate to override the cache of other crates belonging to the same registry.&lt;/p&gt;
&lt;p&gt;## Mitigations&lt;/p&gt;
&lt;p&gt;Rust 1.96.0, to be released on May 28th, 2026, will update Cargo to reject extracting *any* symlink within crate tarballs, regardless of whether they come from crates.io (which already forbids them) or third-party registries. Note that Cargo never added symlinks when running `cargo package` or `cargo publish`, so the impact of this should be minimal.&lt;/p&gt;
&lt;p&gt;Users who are not able to upgrade to the most recent Rust version are recommended to audit the contents of t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jq42-7mfv-hm57</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-5223 — Crates in third party registries can override the cached source of other crates</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-5223</link>
      <description>msrc_CVE-2026-5223</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-5223</guid>
    </item>
    <item>
      <title>RHSA-2026:42923 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:42923</link>
      <description>&lt;p&gt;cargo: Cargo: Source code overwrite due to symlink mishandling in third-party registries cmov: cmov: Incorrect output due to improper zero-extension in aarch64 conditional move operations&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;cargo: Cargo: Source code overwrite due to symlink mishandling in third-party registries cmov: cmov: Incorrect output due to improper zero-extension in aarch64 conditional move operations&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:42923</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-5223</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-5223</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: rustc, Ubuntu:Pro:16.04:LTS: cargo, Ubuntu:Pro:16.04:LTS: rustc, Ubuntu:Pro:18.04:LTS: cargo, Ubuntu:Pro:18.04:LTS: rustc, Ubuntu:Pro:20.04:LTS: cargo, Ubuntu:Pro:20.04:LTS: rustc, Ubuntu:Pro:20.04:LTS: rustc-1.76, Ubuntu:Pro:20.04:LTS: rustc-1.77, Ubuntu:Pro:20.04:LTS: rustc-1.78 and 37 more&lt;/p&gt;
&lt;p&gt;Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a malicious crate to override the source code of another crate from the same registry. The severity of the vulnerability is **medium** for users of third-party registries. Users of crates.io are **not affected**, as crates.io forbids uploading crates containing any symlink.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: rustc, Ubuntu:Pro:16.04:LTS: cargo, Ubuntu:Pro:16.04:LTS: rustc, Ubuntu:Pro:18.04:LTS: cargo, Ubuntu:Pro:18.04:LTS: rustc, Ubuntu:Pro:20.04:LTS: cargo, Ubuntu:Pro:20.04:LTS: rustc, Ubuntu:Pro:20.04:LTS: rustc-1.76, Ubuntu:Pro:20.04:LTS: rustc-1.77, Ubuntu:Pro:20.04:LTS: rustc-1.78 and 37 more&lt;/p&gt;
&lt;p&gt;Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a malicious crate to override the source code of another crate from the same registry. The severity of the vulnerability is **medium** for users of third-party registries. Users of crates.io are **not affected**, as crates.io forbids uploading crates containing any symlink.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-5223</guid>
    </item>
  </channel>
</rss>
