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 79% 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.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
21.3%
KEV
Not listed

Published

May 25, 2026

Last Modified

June 1, 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(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 55× 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 103 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-13 22:31 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-05 02:31 UTCEPSS rescore
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-01 15:07 UTCEPSS rescore
Show 75 more
  1. 2026-06-30 23:22 UTCEPSS rescore
  2. 2026-06-29 02:13 UTCEG score recompute
  3. 2026-06-29 02:13 UTCVendor advisory
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 20:33 UTCEG score recompute
  7. 2026-06-27 20:33 UTCVendor advisory
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-26 18:57 UTCEG score recompute
  10. 2026-06-26 18:57 UTCVendor advisory
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-25 13:38 UTCEG score recompute
  13. 2026-06-25 13:38 UTCVendor advisory
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-23 21:33 UTCEPSS rescore
  16. 2026-06-23 21:33 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-19 19:26 UTCEPSS rescore
  24. 2026-06-19 19:26 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
  26. 2026-06-18 17:52 UTCEPSS rescore
  27. 2026-06-18 03:58 UTCEG score recompute
  28. 2026-06-17 17:53 UTCEPSS rescore
  29. 2026-06-17 02:22 UTCEG score recompute
  30. 2026-06-16 17:53 UTCEPSS rescore
  31. 2026-06-16 00:48 UTCEG score recompute
  32. 2026-06-16 00:48 UTCVendor advisory
  33. 2026-06-15 17:49 UTCEPSS rescore
  34. 2026-06-15 17:49 UTCEPSS rescore
  35. 2026-06-14 23:18 UTCEPSS rescore
  36. 2026-06-14 23:12 UTCEG score recompute
  37. 2026-06-14 23:12 UTCVendor advisory
  38. 2026-06-13 23:00 UTCEPSS rescore
  39. 2026-06-13 21:38 UTCEG score recompute
  40. 2026-06-12 23:12 UTCEPSS rescore
  41. 2026-06-12 23:12 UTCEPSS rescore
  42. 2026-06-12 19:44 UTCEG score recompute
  43. 2026-06-11 18:10 UTCEG score recompute
  44. 2026-06-11 14:00 UTCEPSS rescore
  45. 2026-06-10 22:19 UTCEPSS rescore
  46. 2026-06-10 16:34 UTCEG score recompute
  47. 2026-06-10 13:22 UTCEPSS rescore
  48. 2026-06-09 15:00 UTCEG score recompute
  49. 2026-06-08 14:17 UTCEPSS rescore
  50. 2026-06-08 13:25 UTCEG score recompute
  51. 2026-06-07 15:25 UTCEPSS rescore
  52. 2026-06-07 11:51 UTCEG score recompute
  53. 2026-06-06 13:47 UTCEPSS rescore
  54. 2026-06-06 10:17 UTCEG score recompute
  55. 2026-06-05 22:47 UTCEPSS rescore
  56. 2026-06-05 08:42 UTCEG score recompute
  57. 2026-06-05 06:10 UTCEPSS rescore
  58. 2026-06-05 06:10 UTCEPSS rescore
  59. 2026-06-04 07:07 UTCEG score recompute
  60. 2026-06-03 05:32 UTCEG score recompute
  61. 2026-06-02 20:13 UTCEPSS rescore
  62. 2026-06-02 03:57 UTCEG score recompute▼ 1.20
  63. 2026-06-01 13:52 UTCEPSS rescore
  64. 2026-06-01 13:52 UTCEPSS rescore
  65. 2026-06-01 02:22 UTCEG score recompute
  66. 2026-05-31 22:30 UTCEPSS rescore
  67. 2026-05-31 22:30 UTCEPSS rescore
  68. 2026-05-31 00:16 UTCEPSS rescore
  69. 2026-05-31 00:16 UTCEPSS rescore
  70. 2026-05-29 13:44 UTCEPSS rescore
  71. 2026-05-29 13:44 UTCEPSS rescore
  72. 2026-05-28 13:44 UTCEPSS rescore
  73. 2026-05-28 13:44 UTCEPSS rescore
  74. 2026-05-27 13:40 UTCEPSS rescore
  75. 2026-05-27 13:40 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 June 1, 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 21.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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