CVE-2026-61081

LOWPre-NVD 2.72.7
EchelonGraph scoreMEDIUM confidence

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

Score 2.7 from GitHub Security Advisory (severity: LOW) published 2026-07-22. A secondary CVSS source baseline 2.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
2.7EG
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.3%CVSS: 2.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Performance Schema). 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 read access to a subset of MySQL Server, MySQL Cluster accessible data. CVSS 3.1 Base Score 2.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N).

CVSS v3
2.7
EG Score
2.7LOWmedium confidence
EG Risk
12
EG Risk 12/100

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 (value × EchelonGraph’s weight)
Severity27% × 45%
The EG Score, 2.7 of 10.
Exploitation0.3% × 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.3%
EPSS %ILE
16th
KEV
Not listed

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)

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntumysql-testsuite (8.4.11-0ubuntu0.26.04.1) @ resolute2026-10-01ubuntu
redhatmysql:8.4-9080020260812072812.rhel92026-08-19redhat
redhatmysql:8.4-8100020260812072430.489197e62026-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 12× in last 7d / 42× 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 132 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 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-61081?
CVE-2026-61081 is a low-severity vulnerability; its CVE record was published on July 21, 2026. Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Performance Schema). 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 the CVE record for CVE-2026-61081 published?
The CVE record for CVE-2026-61081 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-61081 actively exploited?
CVE-2026-61081 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61081?
CVE-2026-61081 has a CVSS base score of 2.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61081?
A fix for CVE-2026-61081 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61081 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-61081

Explore →

Is Your Infrastructure Affected by CVE-2026-61081?

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