CVE-2026-5223

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

May 25, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jun 16, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic
https://groups.google.com/g/rustlang-security-announcements/c/IB74S7Yksg8
github_pr

Fix CVE-2026-5222 and CVE-2026-5223

Fix merged in rust-lang/cargo PR #17031 on 2026-05-25 — awaiting tagged release

https://github.com/rust-lang/cargo/pull/17031
generic

Security Advisory for Cargo (CVE-2026-5223) | Rust Blog

https://blog.rust-lang.org/2026/05/25/cve-2026-5223/

Vendor Advisories for CVE-2026-5223(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrust-main-1.97.1-1.1.hum12026-07-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(13 across 7 ecosystems)
Debian:11(3)
PackageVulnerable rangeFixed inDependents
cargo0.47.0-3 ... 0.70.1-1~exp1 (21 versions)——
rustc1.48.0+dfsg1-2 ... 1.96.0+dfsg1-1~exp1 (200 versions)——
rust-cargo0.43.1-4 ... 0.91.0-4 (34 versions)——
Debian:12(3)
PackageVulnerable rangeFixed inDependents
cargo0.66.0+ds1-1 ... 0.70.1-1~exp1 (8 versions)——
rustc1.63.0+dfsg1-2 ... 1.96.0+dfsg1-1~exp1 (144 versions)——
rust-cargo0.66.0-1 ... 0.91.0-4 (29 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
rustc1.85.0+dfsg3-1 ... 1.96.0+dfsg1-1~exp1 (50 versions)——
rust-cargo0.86.0-2 ... 0.91.0-4 (7 versions)——
Debian:14(2)
PackageVulnerable rangeFixed inDependents
rustc1.85.0+dfsg3-1 ... 1.95.0+dfsg1-1 (47 versions)1.95.0+dfsg1-2—
rust-cargo0.86.0-2, 0.86.0-3, 0.86.0-4, 0.91.0-1, 0.91.0-20.91.0-3—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
rust—1.91.1-r2—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
rust—1.96.0-r0—
crates.io(1)
PackageVulnerable rangeFixed inDependents
cargo—0.97.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 174 total refreshes for this CVE.

  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-27 14:25 UTCEPSS rescore
  9. 2026-08-26 14:46 UTCEPSS rescore
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-23 16:34 UTCEG score recompute
  12. 2026-08-23 16:34 UTCVendor advisory
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 21:35 UTCEG score recompute
  16. 2026-08-21 21:35 UTCVendor advisory
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 18:28 UTCEG score recompute
  19. 2026-08-20 18:28 UTCVendor advisory
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-17 09:40 UTCEG score recompute
  24. 2026-08-17 09:40 UTCVendor advisory
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 03:13 UTCEG score recompute
  2. 2026-08-16 03:13 UTCVendor advisory
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 12:59 UTCEG score recompute
  5. 2026-08-14 12:59 UTCVendor advisory
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 11:23 UTCEG score recompute
  8. 2026-08-13 11:23 UTCVendor advisory
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-12 09:49 UTCEG score recompute
  11. 2026-08-12 09:49 UTCVendor advisory
  12. 2026-08-11 07:05 UTCEG score recompute
  13. 2026-08-11 07:05 UTCVendor advisory
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 05:28 UTCEG score recompute
  16. 2026-08-10 05:28 UTCVendor advisory
  17. 2026-08-09 13:46 UTCEPSS rescore
  18. 2026-08-09 03:54 UTCEG score recompute
  19. 2026-08-09 03:54 UTCVendor advisory
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-08 02:20 UTCEG score recompute
  22. 2026-08-08 02:20 UTCVendor advisory
  23. 2026-08-07 00:46 UTCEG score recompute
  24. 2026-08-07 00:46 UTCVendor advisory
  25. 2026-08-06 13:47 UTCEPSS rescore
  26. 2026-08-05 21:08 UTCEG score recompute
  27. 2026-08-05 21:08 UTCVendor advisory
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-04 15:10 UTCEPSS rescore
  30. 2026-08-04 10:39 UTCEPSS rescore
  31. 2026-08-03 20:09 UTCEG score recompute
  32. 2026-08-03 20:09 UTCVendor advisory
  33. 2026-08-03 10:36 UTCEPSS rescore
  34. 2026-08-02 18:33 UTCEG score recompute
  35. 2026-08-02 18:33 UTCVendor advisory
  36. 2026-08-02 02:27 UTCEPSS rescore
  37. 2026-08-01 16:58 UTCEG score recompute
  38. 2026-08-01 16:58 UTCVendor advisory
  39. 2026-08-01 04:16 UTCEPSS rescore
  40. 2026-07-30 16:28 UTCEPSS rescore
  41. 2026-07-30 01:30 UTCEPSS rescore
  42. 2026-07-30 01:30 UTCEPSS rescore
  43. 2026-07-29 17:16 UTCEG score recompute
  44. 2026-07-29 17:16 UTCVendor advisory
  45. 2026-07-28 15:37 UTCEPSS rescore
  46. 2026-07-27 14:14 UTCEPSS rescore
  47. 2026-07-26 14:54 UTCEPSS rescore
  48. 2026-07-26 14:54 UTCEPSS rescore
  49. 2026-07-26 08:00 UTCEG score recompute
  50. 2026-07-26 08:00 UTCVendor advisory
  51. 2026-07-25 14:18 UTCEPSS rescore
  52. 2026-07-25 14:18 UTCEPSS rescore
  53. 2026-07-24 14:18 UTCEPSS rescore
  54. 2026-07-24 14:18 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 14:18 UTCEPSS rescore
  57. 2026-07-23 03:19 UTCEG score recompute
  58. 2026-07-22 14:08 UTCEPSS rescore
  59. 2026-07-22 14:08 UTCEPSS rescore
  60. 2026-07-21 15:25 UTCEPSS rescore
  61. 2026-07-21 15:25 UTCEPSS rescore
  62. 2026-07-20 17:08 UTCEPSS rescore
  63. 2026-07-19 14:31 UTCEPSS rescore
  64. 2026-07-19 02:29 UTCEPSS rescore
  65. 2026-07-18 10:04 UTCEPSS rescore
  66. 2026-07-16 17:03 UTCEPSS rescore
  67. 2026-07-15 16:57 UTCEPSS rescore
  68. 2026-07-15 16:57 UTCEPSS rescore
  69. 2026-07-15 02:00 UTCEPSS rescore
  70. 2026-07-15 02:00 UTCEPSS rescore
  71. 2026-07-13 22:31 UTCEPSS rescore
  72. 2026-07-13 06:13 UTCEPSS rescore
  73. 2026-07-13 06:13 UTCEPSS rescore
  74. 2026-07-12 05:46 UTCEPSS rescore
  75. 2026-07-11 08:27 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-5223?
CVE-2026-5223 is a medium vulnerability published on May 25, 2026. 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…
When was CVE-2026-5223 disclosed?
CVE-2026-5223 was first published in the National Vulnerability Database on May 25, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5223 actively exploited?
CVE-2026-5223 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.4% of all scored CVEs.
What is the CVSS score of CVE-2026-5223?
CVE-2026-5223 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-5223?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5223, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-5223

Explore →

Is Your Infrastructure Affected by CVE-2026-5223?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs