CVE-2026-5222

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 60% 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

Cargo between 1.68 and 1.96 incorrectly normalized the URLs of third-party registries using the sparse index protocol. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the credentials of others users of the same registry. The severity of the vulnerability is low, due to the extremely niche requirements needed to achieve the attack.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

May 25, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jun 13, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic
https://groups.google.com/g/rustlang-security-announcements/c/SfUxOiIdY5s
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-5222) | Rust Blog

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

Vendor Advisories for CVE-2026-5222(2)

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

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

Frequently asked(5)

What is CVE-2026-5222?
CVE-2026-5222 is a medium vulnerability published on May 25, 2026. Cargo between 1.68 and 1.96 incorrectly normalized the URLs of third-party registries using the sparse index protocol. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the…
When was CVE-2026-5222 disclosed?
CVE-2026-5222 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-5222 actively exploited?
CVE-2026-5222 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 60.5% of all scored CVEs.
What is the CVSS score of CVE-2026-5222?
CVE-2026-5222 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-5222?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5222, 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-5222

Explore →

Is Your Infrastructure Affected by CVE-2026-5222?

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

Start Free Scan →Browse All CVEs