CVE-2026-5223: Crates in third party registries can override the cached source of other crates
Rust Project · Cargo
Vendor fix available · Affected: Rust Project Cargo · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 22% of scored CVEs
DescriptionCVE.org
Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a malicious crate to override the source code of another crate from the same registry. The severity of the vulnerability is medium for users of third-party registries. Users of crates.io are not affected, as crates.io forbids uploading crates containing any symlink.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Rust Project · Cargofrom 1.0.0 before 1.96.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Published
- May 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-5223 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.