CVE-2026-5223
Cargo incorrectly handled symlinks inside of crate tarballs …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- blog.rust-lang.org/2026/05/25/cve-2026-5223/
- github.com/rust-lang/cargo/pull/17031
- groups.google.com/g/rustlang-security-announcements/c/IB74S7Yksg8
- github.com/rust-lang/cargo/security/advisories/GHSA-jq42-7mfv-hm57
- nvd.nist.gov/vuln/detail/CVE-2026-5223
- blog.rust-lang.org/2026/05/25/cve-2026-5223
- github.com/advisories/GHSA-jq42-7mfv-hm57
- nvd.nist.gov/vuln/detail/CVE-2026-5223
- cve.org/CVERecord?id=CVE-2026-5223
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.