CVE-2026-22005: Medium severity Oracle MySQL Server vulnerability

Published Apr 21, 2026
·
Updated

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). 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).

Affected Software

6 affected componentsFixes available
Oracle MySQL Server>=8.0.0<=8.0.45, >=8.4.0<=8.4.8, >=9.0.0<=9.6.0
Oracle MySQL Server>=8.0.0<=8.0.45
Oracle MySQL Server>=8.4.0<=8.4.8
Oracle MySQL Server>=9.0.0<=9.6.0
Microsoft azl3 mysql 8.0.45-2
Microsoft cbl2 mysql 8.0.45-3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    If remote connections are not required, set bind-address to 127.0.0.1 in my.cnf/my.ini and restart MySQL to restrict network access to localhost only.

    MySQL Server bind-address = 127.0.0.1
  2. Configuration

    If remote client connections are not needed, enable skip-networking in my.cnf/my.ini and restart MySQL to disable TCP/IP networking.

    MySQL Server skip-networking = ON
  3. Compensating control

    Restrict network access to MySQL ports (e.g., 3306 and any other exposed protocols) at the network perimeter and host firewalls to only trusted management IPs or internal networks.

  4. Operational

    Review and remove or reduce unnecessary high-privileged MySQL accounts; where possible replace high-privilege access with least-privilege accounts. Rotate credentials for privileged accounts if compromise is suspected.

  5. Operational

    Monitor MySQL servers for hangs, crashes, and frequent restarts (enable alerting on availability anomalies) and collect crash logs/core dumps for investigation if the issue is observed.

Event History

Apr 21, 2026
CVE Published
via MITRE·08:35 PM
Data Sourced
via MITRE·08:35 PM
DescriptionSeverity
Data Sourced
via Red Hat·09:03 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Apr 23, 2026
Data Sourced
via Microsoft·08:03 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:03 AM
Affected Software
Updated
via Microsoft·08:03 AM
Severity

Frequently Asked Questions

1

What is the severity of CVE-2026-22005?

CVE-2026-22005 is considered a high severity vulnerability due to its potential for exploitation by attackers with high privileges.

2

How do I fix CVE-2026-22005?

To fix CVE-2026-22005, upgrade your MySQL Server to a version beyond 8.0.45, 8.4.8, or 9.6.0 as applicable.

3

What versions of MySQL Server are affected by CVE-2026-22005?

CVE-2026-22005 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.

4

Can CVE-2026-22005 be exploited remotely?

Yes, CVE-2026-22005 can be exploited remotely by high privileged attackers with network access.

5

What components of MySQL Server does CVE-2026-22005 affect?

CVE-2026-22005 affects the Optimizer component of the MySQL Server product.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203