CVE-2026-5222: Cargo between 1.68 and 1.96 incorrectly normalized the URLs of third-party registries using the sparse index p

Routine

MEDIUM 6.5UPGRADE

CVE-2026-5222 is a medium-severity flaw (CVSS 6.5) affecting cargo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-647
Published	2026-05-25
Last modified	2026-07-23

Publisher (CNA): rust · Vendor: rust-lang

Last updated 2026-07-23 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-25 10:16 UTCPublished CVE record published
2026-07-23 17:10 UTCUpdated Record last modified

rust-lang cargo UPGRADE

Affected: >= 1.68.0 and < 1.96.0

Fixed in: 1.96.0

Safe to downgrade to: a release before 1.68.0

1. Check installed version

apt-cache policy cargo || rpm -q cargo || cargo --version

2. UPGRADE to 1.96.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade cargo

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade cargo

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.68.0 (Debian / Ubuntu)

apt-cache madison cargo sudo apt install cargo=<VERSION_BEFORE_1.68.0> sudo apt-mark hold cargo

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list cargo sudo dnf downgrade cargo-<VERSION_BEFORE_1.68.0> sudo dnf versionlock add cargo

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-5222?

cargo: upgrade to 1.96.0. Exact commands for each OS are on this page.

Is CVE-2026-5222 being exploited?

CVE-2026-5222 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-5222 affect?

CVE-2026-5222 affects cargo. Severity is medium (CVSS 6.5). 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 a

How urgent is CVE-2026-5222?

Priority 33/100. No elevated risk signals yet.

Related CVEs

CVE-2026-58519 MEDIUM 5.4 UPGRADE Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in The Wiki
CVE-2026-58521 CRITICAL 9.8 UPGRADE Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in The Wiki
CVE-2026-14363 CRITICAL 9.8 UPGRADE Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in The Wiki
CVE-2026-5223 MEDIUM 5.3 UPGRADE Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a

References

← Back to latest CVEs