Bug 2563698 (CVE-2026-119278)

Summary: CVE-2026-119278 org.mariadb.jdbc/mariadb-java-client: MariaDB Connector/J: Denial of Service via malformed authentication response
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: anthomas, ant, aschwart, aszczucz, boliveir, ccranfor, cescoffi, drichtar, eglynn, ehelms, fmongiar, ggainey, gsmet, janstey, jjoyce, jmartisk, jpasqual, jpechane, jpretori, jschluet, juwatts, lhh, manderse, mburns, mdellweg, mgarciac, mhulan, mposolda, nmoumoul, olubyans, osousa, ozzy, pcreech, pjindal, rchan, rguimara, rhel-process-autobot, rmartinc, sbiarozk, smallamp, ssilvert, sthorger, tmalecek, varjain, vmuzikar, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in MariaDB Connector/J. A malicious server or an attacker intercepting network traffic can exploit this vulnerability by sending a malformed authentication response during the connection handshake. Because the driver does not properly validate the response structure, this issue can trigger excessive memory allocation or an unhandled crash, resulting in a Denial of Service (DoS).
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-10-29 21:28:53 UTC 
MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7 and 3.4.5, during caching_sha2_password authentication, the authentication-more-data response was treated as a length-encoded byte array, memory was allocated from the server-declared length, and authResult[0] was accessed without ensuring a byte existed. A malicious or compromised server, or a machine-in-the-middle attacker, could declare a very large length or send an empty response before any password was transmitted. The malformed packet could cause excessive allocation or an unchecked ArrayIndexOutOfBoundsException escaping from DriverManager.getConnection(). This issue is fixed in versions 3.3.7 and 3.4.5.