CVE-2026-61081

LOWPre-NVD 2.72.7
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — Patch released this week
2.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.7Exploit: None knownExposed: 0

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.7(high)
EG Risk
12(Track)
EG Risk 12/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
Severity27% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 27, 2026

References (1)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 54× 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.

  1. 2026-08-19 17:04 UTCEPSS rescore
  2. 2026-08-19 12:14 UTCEG score recompute
  3. 2026-08-19 12:14 UTCVendor advisory
  4. 2026-08-19 12:14 UTCGHSA enrichment
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 06:09 UTCEG score recompute
  9. 2026-08-16 06:09 UTCGHSA enrichment
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 00:07 UTCEG score recompute
  13. 2026-08-13 00:07 UTCGHSA enrichment
  14. 2026-08-12 13:51 UTCEPSS rescore
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-09 18:06 UTCEG score recompute
  17. 2026-08-09 18:06 UTCGHSA enrichment
  18. 2026-08-09 13:47 UTCEPSS rescore
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-06 13:47 UTCEPSS rescore
  21. 2026-08-06 12:05 UTCEG score recompute
  22. 2026-08-06 12:05 UTCGHSA enrichment
  23. 2026-08-05 19:17 UTCEPSS rescore
  24. 2026-08-04 15:10 UTCEPSS rescore
  25. 2026-08-04 10:39 UTCEPSS rescore
Show 29 more
  1. 2026-08-03 10:36 UTCEPSS rescore
  2. 2026-08-03 06:05 UTCEG score recompute
  3. 2026-08-03 06:05 UTCGHSA enrichment
  4. 2026-08-02 02:27 UTCEPSS rescore
  5. 2026-08-01 04:16 UTCEPSS rescore
  6. 2026-07-31 00:03 UTCEG score recompute
  7. 2026-07-31 00:03 UTCGHSA enrichment
  8. 2026-07-30 16:28 UTCEPSS rescore
  9. 2026-07-30 01:30 UTCEPSS rescore
  10. 2026-07-30 01:30 UTCEPSS rescore
  11. 2026-07-28 15:37 UTCEPSS rescore
  12. 2026-07-27 18:00 UTCEG score recompute
  13. 2026-07-27 18:00 UTCGHSA enrichment
  14. 2026-07-27 14:14 UTCEPSS rescore
  15. 2026-07-26 14:54 UTCEPSS rescore
  16. 2026-07-26 14:54 UTCEPSS rescore
  17. 2026-07-26 03:47 UTCEG score recompute
  18. 2026-07-26 03:47 UTCGHSA enrichment
  19. 2026-07-25 14:18 UTCEPSS rescore
  20. 2026-07-25 14:18 UTCEPSS rescore
  21. 2026-07-24 14:18 UTCEPSS rescore
  22. 2026-07-24 14:18 UTCEPSS rescore
  23. 2026-07-23 14:18 UTCEPSS rescore
  24. 2026-07-23 14:18 UTCEPSS rescore
  25. 2026-07-23 03:21 UTCEG score recompute
  26. 2026-07-22 14:08 UTCEPSS rescore
  27. 2026-07-22 14:08 UTCEPSS rescore
  28. 2026-07-21 22:23 UTCEG score recompute
  29. 2026-07-21 22:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61081?
CVE-2026-61081 is a low vulnerability 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 CVE-2026-61081 disclosed?
CVE-2026-61081 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-61081 actively exploited?
CVE-2026-61081 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 84.7% of all scored CVEs.
What is the CVSS score of CVE-2026-61081?
CVE-2026-61081 has a CVSS v3 base score of 2.7 (NVD).
How do I remediate CVE-2026-61081?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61081, 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-61081

Explore →

Is Your Infrastructure Affected by CVE-2026-61081?

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