PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-61144 Oracle Corporation CVE debrief

A vulnerability was found in MySQL Server and MySQL Cluster products of Oracle MySQL. The vulnerability is located in the Server: Optimizer component and affects versions 9.7.0-9.7.1 of both products. A high privileged attacker with network access via multiple protocols can exploit this vulnerability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server and MySQL Cluster. The CVSS 3.1 Base Score is 4.9, indicating a MEDIUM severity. The CVSS Vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H.

Vendor
Oracle Corporation
Product
MySQL Server
CVSS
MEDIUM 4.9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-21
Original CVE updated
2026-07-27
Advisory published
2026-07-21
Advisory updated
2026-07-27

Who should care

Administrators and users of MySQL Server and MySQL Cluster versions 9.7.0-9.7.1 should be aware of this vulnerability and take necessary actions to mitigate the risk. This includes applying patches or updates provided by Oracle, restricting access to the MySQL Server and MySQL Cluster to only necessary personnel, and monitoring the system for any suspicious activity.

Technical summary

The vulnerability is caused by a weakness in the Server: Optimizer component of MySQL Server and MySQL Cluster. The vulnerability can be exploited remotely with high privileges, and the impact is on availability. The CVSS Vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H, indicating that the vulnerability can be exploited remotely with high privileges, and the impact is on availability. This vulnerability affects MySQL Server and MySQL Cluster versions 9.7.0-9.7.1.

Defensive priority

Medium priority should be given to patching or mitigating this vulnerability, as it can be exploited by high privileged attackers to cause a denial of service.

Recommended defensive actions

  • Apply the patches or updates provided by Oracle to fix the vulnerability.
  • Restrict access to the MySQL Server and MySQL Cluster to only necessary personnel.
  • Monitor the system for any suspicious activity.
  • Consider implementing additional security measures to prevent exploitation.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record was published on 2026-07-21T22:18:45.763Z and was last modified on 2026-07-27T17:40:37.907Z. The NVD entry is currently Analyzed. This vulnerability affects MySQL Server and MySQL Cluster versions 9.7.0-9.7.1. The vulnerability is located in the Server: Optimizer component. A high privileged attacker with network access via multiple protocols can exploit this vulnerability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server and MySQL Cluster. The CVSS 3.1 Base Score is 4.9, indicating a MEDIUM severity. The CVSS Vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H. Administrators and users of MySQL Server and MySQL Cluster versions 9.7.0-9.7.1 should be aware of this vulnerability and take necessary actions to mitigate the risk.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-61144 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-61144

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-61144 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-61144

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.