CVE-2026-35237: Medium severity Oracle MySQL Server vulnerability
Last updated 6 June 2026
Other sources
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.0-8.0.45, 8.4.0-8.4.8 and 9.0.0-9.6.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. 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).
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/mysql-8.0to a version that resolves this vulnerability.Fixed in 8.0.46-1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-35237?
CVE-2026-35237 is classified as an easily exploitable vulnerability that poses a significant risk to MySQL Server.
How do I fix CVE-2026-35237?
To mitigate CVE-2026-35237, upgrade your MySQL Server to a version beyond 8.0.45, 8.4.8, or 9.6.0.
What versions of MySQL Server are affected by CVE-2026-35237?
CVE-2026-35237 affects MySQL Server versions 8.0.0 to 8.0.45, 8.4.0 to 8.4.8, and 9.0.0 to 9.6.0.
Who can exploit CVE-2026-35237?
CVE-2026-35237 can be exploited by a high privileged attacker with network access via multiple protocols.
Is CVE-2026-35237 a critical vulnerability?
Yes, CVE-2026-35237 is considered critical due to its ability to compromise MySQL Server with high privileges.