CVE-2026-22005

MEDIUMNVD 4.94.9—
EchelonGraph scoreMEDIUM confidence

Score 4.9 from GitHub Security Advisory published 2026-04-21. NVD baseline CVSS 4.9; sources differ by 0.0.

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

A fix is available — apply it.

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.0-8.0.45, 8.4.0-8.4.8 and 9.0.0-9.6.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

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

Published

April 21, 2026

Last Modified

April 23, 2026

References (1)

Vendor Advisories for CVE-2026-22005(1)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmysql:8.4-8100020260526091138.489197e62026-06-16redhat
redhatmysql:8.0-8100020260609092222.489197e62026-06-15redhat
ubuntumysql-testsuite-8.0 (8.0.46-0ubuntu0.20.04.1+esm2) @ focal2026-06-14ubuntu
ubuntumysql-testsuite (8.4.9-0ubuntu0.26.04.1) @ resolute2026-06-14ubuntu
redhatmysql:8.4-9080020260602140041.rhel92026-06-10redhat
redhatmysql-0:8.0.46-1.el9_82026-06-04redhat
redhatmysql8.4-0:8.4.9-1.el10_22026-05-26redhat

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 25× 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 208 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-22005?
CVE-2026-22005 is a medium vulnerability published on April 21, 2026. Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.0-8.0.45, 8.4.0-8.4.8 and 9.0.0-9.6.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise…
When was CVE-2026-22005 disclosed?
CVE-2026-22005 was first published in the National Vulnerability Database on April 21, 2026, with the most recent update on April 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-22005 actively exploited?
CVE-2026-22005 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 74.8% of all scored CVEs.
What is the CVSS score of CVE-2026-22005?
CVE-2026-22005 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2026-22005?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22005, 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-22005

Explore →

Is Your Infrastructure Affected by CVE-2026-22005?

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

Start Free Scan →Browse All CVEs