PatchSiren cyber security CVE debrief
CVE-2026-61108 Oracle Corporation CVE debrief
A vulnerability was discovered in the MySQL Server and MySQL Cluster products of Oracle MySQL, specifically in the Server: GIS component. The affected versions are MySQL Server 9.7.0-9.7.1 and MySQL Cluster 9.7.0-9.7.1. This vulnerability allows a low-privileged attacker with network access via multiple protocols to compromise MySQL Server and MySQL Cluster. Successful attacks can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server and MySQL Cluster. The vulnerability has a medium severity with a CVSS 3.1 Base Score of 6.5.
- Vendor
- Oracle Corporation
- Product
- MySQL Server
- CVSS
- MEDIUM 6.5
- 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 precautions to mitigate the risk. This includes reviewing system configurations, monitoring for unusual activity, and applying patches or updates provided by Oracle.
Technical summary
The vulnerability has a CVSS 3.1 Base Score of 6.5, indicating a medium severity. The CVSS Vector is (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). The vulnerability is classified under CWE-400. It affects MySQL Server: 9.7.0-9.7.1 and MySQL Cluster: 9.7.0-9.7.1, allowing a low-privileged attacker with network access via multiple protocols to compromise MySQL Server and MySQL Cluster, potentially leading to a complete DOS.
Defensive priority
Medium priority should be given to patching or mitigating this vulnerability, as it can lead to a complete DOS of MySQL Server and MySQL Cluster. Defenders should focus on applying patches, restricting network access, and monitoring systems for unusual activity.
Recommended defensive actions
- Apply patches or updates provided by Oracle to fix the vulnerability.
- Restrict network access to MySQL Server and MySQL Cluster to only necessary personnel.
- Monitor MySQL Server and MySQL Cluster for unusual activity or crashes.
- Consider implementing compensating controls, such as intrusion detection and prevention systems.
- Review system configurations to ensure they align with security best practices.
- Perform a thorough review of asset inventory to identify potentially exposed systems.
- Track exceptions and retest remediated assets to ensure the vulnerability is properly mitigated.
Evidence notes
The CVE record was published on 2026-07-21T22:18:42.037Z and was last modified on 2026-07-27T17:41:46.803Z. The NVD entry is currently Analyzed. This information is based on the provided source corpus. Further verification by defenders is recommended to ensure accurate understanding of the vulnerability.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-61108 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-61108
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-61108 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-61108
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://www.oracle.com/security-alerts/cpujul2026.html
[email protected] - Vendor Advisory
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.