CVE-2026-101779 in MySQL Cluster
Summary
by MITRE • 10/21/2026
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Telemetry). 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.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 partial denial of service (partial DOS) of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 2.7 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L).
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 10/21/2026
The identified vulnerability resides within the Telemetry component of Oracle MySQL Server and MySQL Cluster products, specifically affecting versions ranging from 8.4.0 to 8.4.12, 9.7.0 to 9.7.3, and 26.7.0 to 26.7.1 for both server editions. This component is responsible for collecting and transmitting operational data regarding the database instance's performance and health metrics. The flaw represents a significant reliability issue that can be triggered by high-privileged attackers who possess network access through multiple protocols, including TCP/IP connections commonly used for administrative tasks or application connectivity. Although the vulnerability requires authentication due to its reliance on high privilege levels, it remains easily exploitable once an attacker has established valid credentials within the system environment.
From a technical perspective, this flaw is classified under CWE-400, which denotes uncontrolled resource consumption leading to denial of service conditions. The specific manifestation involves the Telemetry subsystem failing to properly manage resources during data collection or transmission processes when subjected to certain inputs or operational states initiated by an authenticated user. This failure results in a partial denial of service, meaning that while the database engine may not crash entirely, critical operations such as query processing, connection handling, or telemetry reporting can become severely degraded or unresponsive for specific sessions or subsystems. The impact is primarily on availability rather than confidentiality or integrity, aligning with the CVSS 3.1 base score of 2.7 which emphasizes low severity due to the high privilege requirement and partial nature of the service disruption.
The operational impact of this vulnerability centers on the potential degradation of database performance for legitimate users sharing resources with the compromised session. Since MySQL is often deployed in production environments handling critical business data, even a partial denial of service can lead to increased latency, timeout errors for client applications, and reduced throughput during peak usage periods. Attackers leveraging this flaw could disrupt ongoing transactions or cause intermittent unavailability that complicates troubleshooting efforts, as the symptoms may mimic other performance bottlenecks rather than indicating a clear security breach. The ability to exploit this via multiple protocols increases the attack surface, allowing potential abuse through standard SQL connections, administrative interfaces, or cluster communication channels depending on the specific deployment configuration and enabled telemetry features.
Mitigation strategies should focus primarily on patching the affected software versions as soon as possible by applying Oracle Critical Patch Update releases that address this Telemetry component flaw. In environments where immediate patching is not feasible due to maintenance windows or compatibility concerns, administrators can consider disabling non-essential telemetry reporting functions if they are not required for operational monitoring. This reduces the attack surface associated with the vulnerable code path. Additionally, enforcing strict network segmentation and limiting database access to only authorized IP addresses and users helps mitigate the risk of exploitation by ensuring that even if credentials are compromised, remote attackers cannot easily reach the MySQL service endpoints. Regular auditing of user privileges ensures that high-privileged accounts remain protected against unauthorized use, further reducing the likelihood of successful exploitation given the requirement for high privilege levels in this vulnerability's attack vector.