CVE-2026-101610

Description

A flaw was found in MySQL's Server Optimizer component. A remote attacker with high administrative privileges can exploit this vulnerability across network protocols to trigger a complete Denial of Service (DoS). Successful exploitation causes the database server to hang or repeatedly crash, disrupting service availability for legitimate users.

Statement

This vulnerability is rated as Moderate severity because exploitation requires high-level privileges to interact with the database server, significantly constraining the threat scope despite the potential for service unavailability. In typical Red Hat Enterprise Linux environments, MySQL databases are deployed within internal network tiers and access is restricted to authenticated accounts under the principle of least privilege. Although an attacker with administrative credentials could trigger an unexpected daemon crash or hang via the query optimizer, there is no impact on data confidentiality or integrity. Consequently, systems with properly segmented administrative access remain resilient against unauthorized or unprivileged disruption.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.9N/A4.9
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredHighN/AHigh
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

If an attacker can trigger the allocation of the limited resources, but the number or size of the resources is not controlled, then the most common result is denial of service. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment, i.e., the product may slow down, crash due to unhandled errors, or lock out legitimate users. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system.

Access Control,Other

Technical Impact: Bypass Protection Mechanism; Other

In some cases it may be possible to force the product to "fail open" in the event of resource exhaustion. The state of the product -- and possibly the security functionality - may then be compromised.

Frequently Asked Questions

Want to get errata notifications? Sign up here.