CVE-2026-5222: Cargo can be coerced to share credentials between registries
Rust · Cargo
Vendor fix available · Affected: Rust Cargo · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 41% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Rust · Cargofrom 1.68.0 before 1.96.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Published
- May 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-5222 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.