UBUNTU-CVE-2026-101613: Medium severity ubuntu/mysql-5.5 vulnerability
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: DDL). Supported versions that are affected are MySQL Server: 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1; MySQL Cluster: 8.0.0-8.0.49, 8.4.0-8.4.12, 9.7.0-9.7.3 and 26.7.0-26.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 ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/mysql-8.0to a version that resolves this vulnerability.Fixed in 8.0.46-0ubuntu0.22.04.5 - Upgrade
Upgrade
ubuntu/mysql-8.0to a version that resolves this vulnerability.Fixed in 8.0.46-0ubuntu0.24.04.5 - Upgrade
Upgrade
ubuntu/mysql-9.7to a version that resolves this vulnerability.Fixed in 9.7.4-0ubuntu0.26.10.1 - Upgrade
Upgrade
ubuntu/mysql-8.4to a version that resolves this vulnerability.Fixed in 8.4.13-0ubuntu0.26.04.2
Event History
Frequently Asked Questions
What level of access does an attacker need?
Exploitation requires a high-privileged attacker with network access to the affected MySQL Server or MySQL Cluster instance. No user interaction is required.
What is the expected impact of a successful attack?
A successful attack can cause the server or cluster to hang or repeatedly crash, resulting in a complete denial of service. The provided CVSS vector indicates no confidentiality or integrity impact.
How can I determine whether my deployment is affected?
Check whether the deployed upstream MySQL Server or MySQL Cluster version falls within the affected version ranges. The provided data does not include Ubuntu package-version mappings, so package-specific status cannot be determined from this information alone.