<?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 04:30:15 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-08151</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-08151</link>
      <description>bdu:2026-08151</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-08151</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-5222</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-5222</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-5222</guid>
    </item>
    <item>
      <title>EUVD-2026-321379</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-321379</link>
      <description>EUVD-2026-321379</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-321379</guid>
    </item>
    <item>
      <title>fkie_cve-2026-5222</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-5222</link>
      <description>&lt;p&gt;Cargo between 1.68 and 1.96 incorrectly normalized the URLs of third-party registries using the sparse index protocol. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the credentials of others users of the same registry. The severity of the vulnerability is **low**, due to the extremely niche requirements needed to achieve the attack.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Cargo between 1.68 and 1.96 incorrectly normalized the URLs of third-party registries using the sparse index protocol. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the credentials of others users of the same registry. The severity of the vulnerability is **low**, due to the extremely niche requirements needed to achieve the attack.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-5222</guid>
    </item>
    <item>
      <title>GHSA-p688-r7jv-fm6f — Cargo can be coerced to share credentials between registries</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p688-r7jv-fm6f</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 normalized the URLs of third-party registries using the [sparse index protocol][1]. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the credentials of others users of the same registry.&lt;/p&gt;
&lt;p&gt;This vulnerability is tracked as CVE-2026-5222. The severity of the vulnerability is **low**, due to the extremely niche requirements needed to achieve the attack.&lt;/p&gt;
&lt;p&gt;## Overview&lt;/p&gt;
&lt;p&gt;Originally Cargo only supported storing a registry&amp;#39;s index within git repositories. Most git hosting solutions allow accessing a git repository with or without the `.git` suffix, so Cargo mirrored this behavior when normalizing registry URLs. This allowed credentials for `https://example.com/index` to be used for `https://example.com/index.git`.&lt;/p&gt;
&lt;p&gt;This normalization was unintentionally applied to the new sparse indexes too. Sparse indexes can be hosted on any HTTPS server, which treat URLs ending with `.git` as different URLs than those without the suffix.&lt;/p&gt;
&lt;p&gt;If the following conditions apply:&lt;/p&gt;
&lt;p&gt;* `https://example.com/index` is a sparse index.
* `https://example.com/index` allows crates to depend on crates from any other registry.
* The attacker is able to publish crates on `https://example.com/index`.
* The attacker is able to upload arbitrary files to `https://example.com/index.git`.&lt;/p&gt;
&lt;p&gt;...the attacker could configure `https://example…&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 normalized the URLs of third-party registries using the [sparse index protocol][1]. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the credentials of others users of the same registry.&lt;/p&gt;
&lt;p&gt;This vulnerability is tracked as CVE-2026-5222. The severity of the vulnerability is **low**, due to the extremely niche requirements needed to achieve the attack.&lt;/p&gt;
&lt;p&gt;## Overview&lt;/p&gt;
&lt;p&gt;Originally Cargo only supported storing a registry&amp;#39;s index within git repositories. Most git hosting solutions allow accessing a git repository with or without the `.git` suffix, so Cargo mirrored this behavior when normalizing registry URLs. This allowed credentials for `https://example.com/index` to be used for `https://example.com/index.git`.&lt;/p&gt;
&lt;p&gt;This normalization was unintentionally applied to the new sparse indexes too. Sparse indexes can be hosted on any HTTPS server, which treat URLs ending with `.git` as different URLs than those without the suffix.&lt;/p&gt;
&lt;p&gt;If the following conditions apply:&lt;/p&gt;
&lt;p&gt;* `https://example.com/index` is a sparse index.
* `https://example.com/index` allows crates to depend on crates from any other registry.
* The attacker is able to publish crates on `https://example.com/index`.
* The attacker is able to upload arbitrary files to `https://example.com/index.git`.&lt;/p&gt;
&lt;p&gt;...the attacker could configure `https://example…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p688-r7jv-fm6f</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-5222 — Cargo can be coerced to share credentials between registries</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-5222</link>
      <description>msrc_CVE-2026-5222</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-5222</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-5222</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-5222</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 between 1.68 and 1.96 incorrectly normalized the URLs of third-party registries using the sparse index protocol. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the credentials of others users of the same registry. The severity of the vulnerability is **low**, due to the extremely niche requirements needed to achieve the attack.&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 between 1.68 and 1.96 incorrectly normalized the URLs of third-party registries using the sparse index protocol. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the credentials of others users of the same registry. The severity of the vulnerability is **low**, due to the extremely niche requirements needed to achieve the attack.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-5222</guid>
    </item>
  </channel>
</rss>
