Registry credential disclosure via sparse URL normalization
Published May 25, 2026 · Updated May 25, 2026
Credential disclosure in Rust Cargo 1.68.0 through 1.95.0 allows remote attackers to obtain registry tokens via a crafted sparse index. Registry URL normalization strips the .git suffix from sparse HTTPS URLs, conflating distinct registry identities and reusing credentials. Exploitation requires attacker publication rights, control of the corresponding .git path, permissive cross-registry dependencies, and a victim downloading the crafted crate.
Summary
What happened
Credential disclosure in Rust Cargo 1.68.0 through 1.95.0 allows remote attackers to obtain registry tokens via a crafted sparse index. Registry URL normalization strips the .git suffix from sparse HTTPS URLs, conflating distinct registry identities and reusing credentials. Exploitation requires attacker publication rights, control of the corresponding .git path, permissive cross-registry dependencies, and a victim downloading the crafted crate.
The record
- CVE
- CVE-2026-5222
- Published
- May 25, 2026
- Updated
- May 25, 2026
- Vendor
- Rust
- Product
- Cargo
- Classifications
- CWE-647, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 25, 2026CVE publishedPublication date reported by the CVE source.
- May 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.68.0 <1.96.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo