Loading vulnerability…
CVE-2026-5222 is a low-severity vulnerability in Cargo affecting versions shipped between Rust 1.68 and Rust 1.96. Cargo incorrectly normalized URLs for third-party registries using the sparse index protocol by treating .git-suffixed and non-.git URLs as equivalent, a behavior historically associated with git repository hosting. When applied to sparse registries hosted on generic HTTPS infrastructure, where /index and /index.git may be distinct resources, this could cause Cargo to reuse authentication credentials across different registries on the same domain. Under niche conditions, an attacker able to publish crates in one third-party registry and control the corresponding .git-suffixed sparse registry path could craft dependencies so that Cargo sends a victim's registry token to the attacker-controlled registry endpoint, disclosing credentials for that registry. Users of crates.io are not affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A low severity vulnerability affecting users of third-party registries involving authentication with normalized URLs.
A low-severity credential leakage vulnerability in Cargo where incorrect normalization of sparse registry URLs could cause a victim's Cargo token to be sent to a malicious registry under niche conditions.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.