2.3
LOW CVSS 4.0
CVE-2026-5222
Cargo can be coerced to share credentials between registries
Description

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.

INFO

Published Date :

May 25, 2026, 8:54 a.m.

Last Modified :

May 25, 2026, 8:54 a.m.

Remotely Exploit :

Yes !

Source :

rust
Affected Products

The following products are affected by CVE-2026-5222 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 4.0 LOW 986d4109-89ea-491f-99fd-a8e4803919bd
Solution
Update Cargo to a version that addresses sparse registry URL normalization issues.
  • Update Cargo to a version later than 1.96.
  • Configure registry URLs carefully.
  • Avoid hosting multiple registries on the same domain.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-5222 vulnerability anywhere in the article.

EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.