CVE-2026-60747

MEDIUMPre-NVD 6.26.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-47079 (ENISA EUVD) · GHSA-4xr7-8qqf-4gj7 (GitHub Security Advisories)Source: ENISA EUVD

6.2EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.2Exploit: None knownExposed services: Not assessed

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 unauthenticated attacker with logon to the infrastructure where MySQL Server, MySQL Cluster executes 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 6.2 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

CVSS v3
6.2
EG Score
6.2MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity62% × 45%
Impact severity (EG Severity): CVSS 6.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.2): severity, escalated by confirmed exploitation. This CVE's 6.2 is its impact severity (EG Severity), not escalated.

EG Severity
6.2 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 21, 2026

Last Modified

July 27, 2026

References (1)

Vendor Advisories for CVE-2026-60747(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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntumysql-testsuite-8.0 (8.0.46-0ubuntu0.22.04.4) @ jammy2026-10-22ubuntu
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 rangeFix by version rangeDependents
mariadb1:10.11.11-0+deb12u1 ... 1:11.8.9+ds-4 (57 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb1:11.8.2-1 ... 1:11.8.9+ds-4 (23 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb1:11.8.2-1 ... 1:11.8.8-1 (16 versions)
  • every version up to 1:11.8.9+ds-1: fixed in 1:11.8.9+ds-1
—

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 10× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 220 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-60747?
CVE-2026-60747 is a medium-severity vulnerability; its CVE record was 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…
When was the CVE record for CVE-2026-60747 published?
The CVE record for CVE-2026-60747 was published on July 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 27, 2026; the record at its source may have been updated since.
Is CVE-2026-60747 actively exploited?
CVE-2026-60747 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-60747?
CVE-2026-60747 has a CVSS base score of 6.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-60747?
A fix for CVE-2026-60747 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-60747 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-60747?

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

Book a Demo →Browse All CVEs