Live › vulnerability › CVE-2026-119278
MariaDB Connector/J, the Java driver for MariaDB and MySQL, mishandles a server response during caching_sha2_password authentication. A malicious server or a man-in-the-middle can send a packet that forces a huge memory allocation or an unhandled exception from DriverManager.getConnection().
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 21:26 UTC. All times on this page are UTC.
Applications that use Connector/J to open database connections, especially ones that connect to database servers outside their control or over networks where traffic can be intercepted. Exposure depends on the authentication path (caching_sha2_password) being used, which is the default for MySQL 8 and newer servers. Teams that run only against trusted, internal database servers over protected links face lower risk but should still upgrade.
No product ranges from the sources yet.
Unknown from the sources.
3.3.7 on the 3.3 line.3.4.5 on the 3.4 line.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-119278")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.