Skip to main content
Mallory
LowVulnerability

CVE-2026-5222: Cargo Sparse Registry Credential Disclosure via URL Normalization

Published May 25, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS2.3Low · v4
EPSS0.48%42nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
RustLang
IdentifiersCVE-2026-5222CWE-200

CVE-2026-5222 is a low-severity information-disclosure vulnerability in Cargo versions shipped with Rust 1.68 through versions before Rust 1.96. Cargo applied Git-oriented normalization that strips a .git suffix to third-party registry URLs using the sparse index protocol. On generic HTTPS hosting, sparse registry locations differing only by that suffix can be distinct resources. This normalization can cause Cargo to associate credentials for a legitimate registry with an attacker-controlled registry endpoint and disclose a victim's Cargo token.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can obtain a victim's third-party Cargo registry credential. The exposed token may permit authenticated access to the legitimate registry, subject to that registry's token scope and authorization model. The issue does not affect integrity or availability directly, and users of crates.io are not affected.

Mitigation

If you can’t patch tonight, do this now.

No mitigation is available for affected older Cargo versions. Where an upgrade cannot be performed immediately, avoid using affected third-party sparse registries, particularly registries hosted in shared domains or environments that permit arbitrary registry-path creation and cross-registry dependencies.

Remediation

Patch, then assume compromise.

Upgrade to Rust 1.96 or later. The corrected Cargo behavior strips the .git suffix only for registry URLs using the Git protocol, preventing sparse registries with distinct HTTPS paths from sharing credentials.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
RustLangCargoapplication
FAQ

Frequently asked questions

Is CVE-2026-5222 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-5222 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5222?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-5222.
Is there a patch for CVE-2026-5222?
Upgrade to Rust 1.96 or later. The corrected Cargo behavior strips the .git suffix only for registry URLs using the Git protocol, preventing sparse registries with distinct HTTPS paths from sharing credentials.
What products are affected by CVE-2026-5222?
RustLang Cargo.
How severe is CVE-2026-5222?
CVE-2026-5222 has a CVSS v4 score of 2.3 (Low) and an EPSS score of 0.48% (42nd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+7 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity14Community discussion across Reddit, Mastodon, and other social sources.