RHSA-2026:99720
Vulnerability from csaf_redhat - Published: 2026-11-12 20:37 - Updated: 2026-11-13 05:18A flaw was found in the MySQL Server optimizer component. A remote attacker with high privileges and network access can exploit this vulnerability through multiple protocols to cause the service to hang or crash repeatedly. Successful exploitation results in a complete Denial of Service (DoS), making the database unavailable to legitimate users.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-0:8.4.13-1.el10_3.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-common-0:8.4.13-1.el10_3.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-debuginfo-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-debuginfo-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-debuginfo-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-debuginfo-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-debugsource-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-debugsource-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-debugsource-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-debugsource-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-devel-debuginfo-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-devel-debuginfo-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-devel-debuginfo-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-devel-debuginfo-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-errmsg-0:8.4.13-1.el10_3.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-libs-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-libs-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-libs-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-libs-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-libs-debuginfo-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-libs-debuginfo-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-libs-debuginfo-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-libs-debuginfo-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-server-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-server-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-server-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-server-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-server-debuginfo-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-server-debuginfo-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-server-debuginfo-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-server-debuginfo-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-test-debuginfo-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-test-debuginfo-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-test-debuginfo-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-10.3.Z:mysql8.4-test-debuginfo-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-debuginfo-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-debuginfo-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-debuginfo-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-debuginfo-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-debugsource-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-debugsource-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-debugsource-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-debugsource-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-devel-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-devel-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-devel-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-devel-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-devel-debuginfo-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-devel-debuginfo-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-devel-debuginfo-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-devel-debuginfo-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-libs-debuginfo-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-libs-debuginfo-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-libs-debuginfo-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-libs-debuginfo-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-server-debuginfo-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-server-debuginfo-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-server-debuginfo-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-server-debuginfo-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-test-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-test-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-test-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-test-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-test-data-0:8.4.13-1.el10_3.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-test-debuginfo-0:8.4.13-1.el10_3.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-test-debuginfo-0:8.4.13-1.el10_3.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-test-debuginfo-0:8.4.13-1.el10_3.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-10.3.Z:mysql8.4-test-debuginfo-0:8.4.13-1.el10_3.x86_64 | — |
Vendor Fix
fix
|
A flaw was found in the MySQL Server Optimizer component. An authenticated remote attacker with low privileges can exploit this vulnerability over the network across multiple protocols. A successful attack allows the attacker to cause the database server to hang or repeatedly crash, leading to a complete Denial of Service (DoS).
A flaw was found in the InnoDB component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
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.
A flaw was found in the InnoDB component of MySQL. A remote attacker with high privileges and network access can exploit this vulnerability to cause the database server to hang or repeatedly crash. This issue results in a complete Denial of Service (DoS), disrupting normal operations and rendering the database unavailable.
A flaw was found in the MySQL InnoDB component. A local, highly privileged attacker with access to the underlying infrastructure, requiring interaction from another user, can exploit this vulnerability to cause a hang or repeatable crash. Successful exploitation results in a Denial of Service (DoS) of the database service.
A flaw was found in the Data Definition Language (DDL) component of MySQL Server and MySQL Cluster. An authenticated attacker with high privileges and network access can exploit this vulnerability to cause the server to hang or crash repeatedly. This flaw primarily results in a complete denial of service (DoS) for the database service.
A flaw was found in the InnoDB component of MySQL. An authenticated attacker with high privileges and network access can exploit this vulnerability to cause the server to hang or repeatedly crash. This issue results in a complete Denial of Service (DoS), rendering the database service unavailable to legitimate users.
A flaw was found in the InnoDB component of MySQL. A local attacker with high privileges on the host infrastructure can exploit this vulnerability to cause the database service to hang or repeatedly crash, resulting in a denial of service (DoS).
A flaw was found in the JSON component of MySQL Server and MySQL Cluster. A remote attacker with low-level privileges and network access can exploit this vulnerability to cause the server to hang or crash repeatedly. Successful exploitation results in a complete Denial of Service (DoS) of the affected database service.
A flaw was found in the InnoDB component of MySQL. An authenticated attacker with high privileges and network access can exploit this vulnerability to cause the database server to hang or repeatedly crash. This issue leads to a complete Denial of Service (DoS), rendering the database service unavailable.
A flaw was found in MySQL. A high-privileged remote attacker with network access can exploit this vulnerability in the InnoDB component to cause a Denial of Service (DoS). Successful exploitation allows the attacker to trigger a hang or repeatable server crash, rendering the database unavailable.
A flaw was found in the InnoDB component of MySQL. A high-privileged attacker with network access could exploit this vulnerability to trigger an unexpected hang or crash of the database server. A successful attack can result in a complete Denial of Service (DoS).
A flaw was found in the InnoDB component of MySQL. A high-privileged remote attacker with network access could exploit this vulnerability to cause a Denial of Service (DoS). Successful attacks can result in an unauthorized hang or repeatable crash of the database service.
A flaw was found in the InnoDB component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the Optimizer component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the InnoDB component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the InnoDB component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the Client programs component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in mysql. A remote attacker with high privileges and network access can exploit this vulnerability to cause a Denial of Service (DoS). By targeting the server component services, the attacker can cause the database to hang or crash repeatedly, disrupting availability for legitimate users.
A flaw was found in the InnoDB component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the C API component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the C API component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in MySQL within the Server Replication component. A remote attacker with high privileges and network access can exploit this vulnerability to trigger an unexpected hang or repeatable crash. This issue results in a complete Denial of Service (DoS), rendering the database service unavailable to legitimate users.
A flaw was found in MySQL's Pluggable Auth component. An authenticated remote attacker with low privileges can exploit this vulnerability over the network across multiple protocols. Successful exploitation allows the attacker to cause the database service to hang or repeatedly crash, resulting in a Denial of Service (DoS).
A flaw was found in the MySQL replication component. A high-privileged remote attacker with network access can exploit this vulnerability to trigger a hang or repeatable crash. Successful exploitation results in a complete Denial of Service (DoS) of the database service.
A flaw was found in the MySQL Server optimizer component. A remote attacker with high privileges can exploit this vulnerability over network protocols to cause the database server to hang or repeatedly crash. This issue results in a complete Denial of Service (DoS) of affected MySQL Server and MySQL Cluster instances.
A flaw was found in the MySQL Server Optimizer. A remote attacker with high privileges can exploit this vulnerability over network protocols to cause the server to hang or crash repeatedly. This issue results in a complete denial of service (DoS) for the database service.
A flaw was found in the Optimizer component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the MySQL JSON component. An authenticated remote attacker with low privileges can exploit this vulnerability over the network using multiple protocols. A successful attack can cause the server to hang or repeatedly crash, resulting in a complete Denial of Service (DoS).
A flaw was found in the InnoDB component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the audit component of MySQL. An authenticated remote attacker with low privileges can exploit this vulnerability over the network across multiple protocols. Successful exploitation allows the attacker to cause a hang or frequently repeatable crash, resulting in a Denial of Service (DoS) for the database service.
A flaw was found in the MySQL Clone Plugin. An authenticated remote attacker with high privileges can exploit this vulnerability over network protocols to trigger an abnormal condition. A successful attack allows the attacker to cause the database server to hang or repeatedly crash, resulting in a Denial of Service (DoS).
A flaw was found in MySQL. An authenticated, remote attacker with high privileges could cause a complete Denial of Service (DoS) by exploiting a vulnerability in the Group Replication component over the network. Successful exploitation causes the server or cluster to hang or crash repeatedly, disrupting database availability.
A flaw was found in MySQL client programs. A remote attacker with high privileges and network access can exploit this vulnerability to compromise the system. Successful exploitation allows the attacker to cause the database server to hang or repeatedly crash, resulting in a complete Denial of Service (DoS).
A flaw was found in the InnoDB component of MySQL. A remote attacker with high privileges and network access can exploit this vulnerability to cause the server to hang or crash repeatedly, resulting in a denial of service (DoS).
A flaw was found in MySQL. An unauthenticated remote attacker with network access via multiple protocols can exploit this vulnerability in the security encryption component to cause the service to hang or crash repeatedly. Successful exploitation results in a complete Denial of Service (DoS).
A flaw was found in the Security: Encryption component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the MySQL replication component. A remote, highly privileged attacker could exploit this vulnerability over the network to cause MySQL Server or MySQL Cluster to hang or crash repeatedly. This issue leads to a complete denial of service (DoS), making the database service unavailable to authorized users.
A flaw was found in the Client programs component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the Client programs component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the Client programs component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the MySQL Group Replication plugin. An unauthenticated attacker located on the adjacent network can exploit this vulnerability to compromise the database service. Successful exploitation primarily allows an attacker to cause a Denial of Service (DoS) by hanging or repeatedly crashing the server, as well as perform unauthorized modifications to accessible data.
A flaw was found in the Pluggable Authentication component of MySQL. An unauthenticated remote attacker could exploit this vulnerability across multiple network protocols to cause the server to hang or crash repeatedly, resulting in a Denial of Service (DoS). In addition, successful exploitation may allow unauthorized modification, insertion, or deletion of accessible database records.
A flaw was found in the MySQL Server replication component. An unauthenticated remote attacker with network access could exploit this vulnerability to create, delete, or modify critical database data. A successful attack can also lead to a Denial of Service (DoS) by causing the server to hang or repeatedly crash.
A flaw was found in the MySQL Group Replication plugin. A remote attacker with high privileges and network access can exploit this vulnerability across multiple protocols. Successful exploitation allows the attacker to cause the service to hang or crash repeatedly, resulting in a complete Denial of Service (DoS).
A flaw was found in the Components Services component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the MySQL Server Telemetry component. A remote attacker with high privileges and network access can exploit this vulnerability over multiple protocols to cause a partial Denial of Service (DoS). Successful exploitation can lead to unauthorized degradation of database service availability.
CWE-400 - Uncontrolled Resource ConsumptionA flaw was found in the MySQL Server X Plugin component. An authenticated remote attacker with low privileges and network access can exploit this vulnerability through network protocol requests. Successful exploitation allows the attacker to cause the database server to hang or repeatedly crash, leading to a complete Denial of Service (DoS).
A flaw was found in MySQL's Group Replication Group Communication System (GCS). An unauthenticated attacker located on the same adjacent network segment can exploit this vulnerability without requiring privileges or user interaction. Successful exploitation allows the attacker to take over the MySQL server, leading to unauthorized data disclosure, data modification, and denial of service.
A flaw was found in the query optimizer component of MySQL Server and MySQL Cluster. An authenticated attacker with high privileges and network access can exploit this vulnerability to cause a Denial of Service (DoS). Successful exploitation allows the attacker to hang or repeatedly crash the database server.
A flaw was found in the MySQL Server JSON component. An authenticated remote attacker with low privileges can exploit this vulnerability over network protocols to modify, create, or delete accessible database records. Successful exploitation can also result in a Denial of Service (DoS) by crashing or hanging the server, as well as unauthorized data disclosure.
A flaw was found in MySQL within the Server Optimizer component. An authenticated remote attacker with high privileges can exploit this vulnerability over the network to cause the database to hang or crash repeatedly. Successful exploitation results in a complete Denial of Service (DoS) for the affected service.
A flaw was found in MySQL Server and MySQL Cluster within the Server Components Services. This vulnerability allows an unauthenticated remote attacker with network access via multiple protocols to cause a Denial of Service (DoS). A successful attack can cause the database server to hang or repeatedly crash.
A flaw was found in the MySQL Optimizer component. An authenticated remote attacker with low privileges can exploit this vulnerability over the network to cause a Denial of Service (DoS). Successful exploitation allows the attacker to hang or repeatedly crash the server, disrupting database operations for legitimate users.
A flaw was found in the XML component of MySQL. An authenticated, low-privileged remote attacker with network access can exploit this vulnerability to cause a Denial of Service (DoS). Successful attacks can result in a hang or frequently repeatable server crash, rendering the database unavailable.
A flaw was found in the Components Services component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the Replication component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the mysqldump component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the MySQL Server optimizer component. A remote attacker with high privileges and network access can exploit this vulnerability by submitting crafted requests across supported protocols. Successful exploitation allows the attacker to cause the database server to hang or crash repeatedly, resulting in a Denial of Service (DoS).
A flaw was found in the Group Replication GCS component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the Security: Privileges component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
A flaw was found in the Server Optimizer component of MySQL. A remote attacker with high privileges can exploit this vulnerability across network protocols to cause the database to hang or repeatedly crash. This issue leads to a complete Denial of Service (DoS), rendering the service unavailable to users.
A flaw was found in the MySQL Server Parser component. An authenticated remote attacker with low privileges can exploit this vulnerability through network access using multiple protocols. A successful attack can cause the service to hang or repeatedly crash, resulting in a Denial of Service (DoS).
A flaw was found in the XML component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
Loading 1.3 MB of JSON…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.