CVE-2026-102466
Description
A flaw was found in the Eclipse Vert.x MySQL client, which can lead to a Denial of Service (DoS). A malicious database server or an attacker positioned on the network can send a crafted result set containing an excessively large column count. Because the client pre-allocates memory for column definitions without validating upper bounds, this triggers an excessive memory allocation that crashes the processing thread and disrupts active connections.
Statement
A denial of service vulnerability of moderate impact was found in the Vert.x MySQL client (vertx-mysql-client) as shipped in Red Hat Build of Quarkus 3 (quarkus-3). The client pre-allocates an array for column definitions based on a server-declared column count without validating an upper bound. A malicious or compromised MySQL server, or an attacker in a man-in-the-middle position on the network path between the application and its database, can send a crafted result set packet declaring an extremely large column count, causing the client to attempt a massive heap allocation. The resulting OutOfMemoryError crashes the Netty event loop thread, disrupting all connections and verticles of the Vert.x application. Red Hat rates this flaw MODERATE (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, 5.9) because exploitation requires conditions outside the attacker's direct control.
The affected vertx-mysql-client component is shipped in Red Hat Build of Quarkus. The quarkus-3.33 stream is affected and the fix is deferred because Red Hat does not file trackers for moderate-severity flaws with a CVSS 3.1 score below 7.0; until a fixed version is delivered, applications that connect to an untrusted, compromised, or network-exposed MySQL server remain exposed to a complete denial of service of the Vert.x application. The quarkus-3.27 stream is also affected but is out of support scope.
The CVE record carries a CVSS 4.0 score of 8.2 (IMPORTANT) from the CVE program, while Red Hat and the upstream Eclipse Vert.x advisory both rate this flaw at 5.9 (MODERATE/medium) using CVSS 3.1. The difference stems from the CVSS 4.0 model producing a higher score for this availability-only flaw and from the high attack complexity: exploitation requires a malicious or compromised database server or a man-in-the-middle position.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Restricting the Vert.x MySQL client to connect only to trusted MySQL servers over secured network paths reduces exposure to the man-in-the-middle attack path, but does not protect against a malicious or compromised database server. The upstream Eclipse Vert.x project has released fixed versions of vertx-mysql-client (4.5.35, 5.1.10, and 5.2.1); Red Hat Build of Quarkus customers should monitor Red Hat advisories for a supported fixed version of this component.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.9 | 5.9 | N/A |
| Attack Vector | Network | Network | N/A |
| Attack Complexity | High | High | N/A |
| Privileges Required | None | None | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | None | None | N/A |
| Integrity Impact | None | None | N/A |
| Availability Impact | High | High | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.