CVE-2026-34267: 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. 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

4 affected componentsFixes available
Oracle MySQL Server>=8.0.0<=8.0.45
Oracle MySQL Server>=8.0.0<=8.0.45
Microsoft cbl2 mysql 8.0.45-3
Microsoft azl3 mysql 8.0.45-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove Oracle MySQL Server from your environment.

    If MySQL Server is not required on a host, uninstall or stop and remove the service to eliminate exposure to the vulnerability.

  2. Configuration

    Configure MySQL to not listen on all interfaces (e.g., set bind-address to 127.0.0.1 or a specific management IP) and disable any unnecessary protocol listeners so the server is not exposed to untrusted networks.

    Oracle MySQL Server bind-address / network listeners = restrict to localhost or specific trusted IPs; disable unnecessary protocol listeners
  3. Configuration

    Revoke or restrict network-access for accounts with high privileges. Ensure administrative/privileged accounts cannot authenticate from untrusted hosts; require use of controlled jump hosts or local access for administration.

    Oracle MySQL Server high_privilege_accounts_remote_access = disabled / restricted
  4. Compensating control

    Restrict access to MySQL network ports and management interfaces to trusted IPs using firewall rules, network ACLs, or segmentation. Block or limit access from untrusted networks and apply ingress filtering to prevent remote exploitation via exposed protocols.

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:05 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Apr 23, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
Affected Software
Updated
via Microsoft·08:02 AM
Severity

Frequently Asked Questions

1

What is the severity of CVE-2026-34267?

CVE-2026-34267 is considered a high severity vulnerability due to its potential to allow high privileged attackers to compromise MySQL Server.

2

How do I fix CVE-2026-34267?

To fix CVE-2026-34267, update your MySQL Server to a version higher than 8.0.45.

3

Who is affected by CVE-2026-34267?

CVE-2026-34267 affects users of Oracle MySQL Server versions 8.0.0 to 8.0.45.

4

What part of MySQL Server is vulnerable in CVE-2026-34267?

CVE-2026-34267 affects the Optimizer component of the MySQL Server.

5

What is the impact of an attack exploiting CVE-2026-34267?

An attack exploiting CVE-2026-34267 can lead to unauthorized access and potential manipulation of the MySQL Server.

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