https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T11:40:51.368856+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-08151 bdu:2026-08151 2026-10-03T11:40:51.473153+00:00 bdu:2026-08151 https://cve.radiocsirt.org/vuln/bell-cve-2026-5222 BELL-CVE-2026-5222 2026-10-03T11:40:51.473193+00:00

Affected: Alpaquita:23: rust, Alpaquita:25: rust, Alpaquita:stream: rust

 https://cve.radiocsirt.org/vuln/euvd-2026-321379 EUVD-2026-321379 2026-10-03T11:40:51.473224+00:00 EUVD-2026-321379 https://cve.radiocsirt.org/vuln/fkie_cve-2026-5222 fkie_cve-2026-5222 2026-10-03T11:40:51.473238+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-p688-r7jv-fm6f GHSA-p688-r7jv-fm6f — Cargo can be coerced to share credentials between registries 2026-10-03T11:40:51.473264+00:00

Affected: crates.io: cargo

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.

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.

## Overview

Originally Cargo only supported storing a registry'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`.

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.

If the following conditions apply:

* `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`.

...the attacker could configure `https://example…

 https://cve.radiocsirt.org/vuln/msrc_cve-2026-5222 msrc_CVE-2026-5222 — Cargo can be coerced to share credentials between registries 2026-10-03T11:40:51.473309+00:00 msrc_CVE-2026-5222 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-5222 UBUNTU-CVE-2026-5222 2026-10-03T11:40:51.473327+00:00

Affected: 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

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.