CVE-2026-47023

MEDIUMPre-NVD 4.94.9—
EchelonGraph scoreMEDIUM confidence

Score 4.9 from GitHub Security Advisory published 2026-07-22. a secondary CVSS source baseline 4.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
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, MySQL Cluster product of Oracle MySQL (component: Server: Replication). Supported versions that are affected are MySQL Server: 8.4.0-8.4.10, 9.7.0-9.7.1; MySQL Cluster: 8.0.0-8.0.47, 8.4.0-8.4.10 and 9.7.0-9.7.1. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster. 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

July 21, 2026

Last Modified

July 27, 2026

References (1)

Vendor Advisories for CVE-2026-47023(4)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntumysql-testsuite (8.4.11-0ubuntu0.26.04.1) @ resolute2026-09-11ubuntu
redhatmysql:8.4-8100020260812072430.489197e62026-08-19redhat
redhatmysql:8.4-9080020260812072812.rhel92026-08-19redhat
redhatmysql8.4-0:8.4.11-1.el10_22026-08-18redhat

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
mariadb1:10.11.11-0+deb12u1 ... 1:11.8.9+ds-1 (54 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
mariadb1:11.8.2-1 ... 1:11.8.9+ds-1 (20 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
mariadb1:11.8.2-1 ... 1:11.8.9+ds-1 (17 versions)——

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 21× in last 7d / 88× 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 146 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47023?
CVE-2026-47023 is a medium vulnerability published on July 21, 2026. Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Replication). Supported versions that are affected are MySQL Server: 8.4.0-8.4.10, 9.7.0-9.7.1; MySQL Cluster: 8.0.0-8.0.47, 8.4.0-8.4.10 and 9.7.0-9.7.1. Easily exploitable vulnerability allows high…
When was CVE-2026-47023 disclosed?
CVE-2026-47023 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47023 actively exploited?
CVE-2026-47023 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-47023?
CVE-2026-47023 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2026-47023?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47023, 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-47023

Explore →

Is Your Infrastructure Affected by CVE-2026-47023?

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

Start Free Scan →Browse All CVEs