Cargo versions 1.68 through 1.96 incorrectly normalize third‑party registry URLs when using the sparse index protocol. This normalization removes the ".git" suffix from URLs, causing redirects that treat different registry sub‑paths as the same host. An attacker who can publish crates to a registry that shares the same domain as other registries can obtain the access credentials (e.g., tokens or passwords) stored for those registries, allowing unauthorized access to packages and potentially sensitive build artifacts. The weakness is classified as CWE‐647, an information exposure through wrong normalization. The vulnerability is deemed low severity because it requires a highly specific setup: a hosting provider that allows multiple registries on the same domain and an attacker who can publish crates.

All installations of Cargo between version 1.68 and 1.96 that use the sparse index protocol for third‑party registries are affected. The impact applies regardless of operating system, as the flaw lies in the Cargo binary itself.

The CVSS score is 2.3 and the EPSS score is not available, indicating a limited likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog. Exploitation would require control of a registry within a domain hosting multiple registries and the ability to publish crates; because of these niche prerequisites, the practical risk remains low.