Skip to main content
← All vulnerabilities
CVE-2026-119278EUVD-2026-113385GHSA-R9VH-XH4R-J6GR

MariaDB Connector/J: Rogue server can crash the client during caching_sha2_password authentication

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 3.3.7, 3.4.5
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

MariaDB Connector/J, the Java driver used to connect applications to MariaDB and MySQL databases, is affected. A malicious or compromised database server, or an attacker positioned in the network path, can send a malformed authentication response that causes the client to crash or consume excessive memory during connection.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

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.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • mariadb-corporation mariadb-connector-j

    From 3.0.0 · fixed in 3.3.7; From 3.4.0 · fixed in 3.4.5

References 5

GitHub · mariadb-corporation/mariadb-connector-j