CVE-2026-119278

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

Published Oct 29, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability arises when MariaDB Connector/J processes the caching_sha2_password authentication response. The driver assumes the authentication‑more‑data packet is a length‑encoded byte array and allocates memory based on the server‑declared length without verifying the packet size. A malicious or compromised server, or an attacker performing a man‑in‑the‑middle attack, can send a packet with an overly large length or an empty response before any password is transmitted. This causes excessive memory allocation or triggers an unchecked ArrayIndexOutOfBoundsException that propagates from DriverManager.getConnection(), resulting in the client application crashing. The flaw leads to a denial of service for the client, and does not provide remote code execution or other higher‑impact capabilities.

Affected Systems

This issue affects MariaDB Connector/J from version 3.0.0 through 3.3.6 and 3.4.4. Applications that use those Connector/J versions to connect Java applications to MariaDB or MySQL databases are susceptible. The vulnerability is resolved in Connector/J 3.3.7 and 3.4.5 and later releases.

Risk and Exploitability

The CVSS score of 5.9 reflects a moderate severity. The EPSS score of < 1% indicates a very low exploitation probability, and the vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog. Exploitation requires a malicious or compromised database server or the ability to intercept the authentication traffic, such as a man‑in‑the‑middle attack. While it does not grant code execution or data exfiltration, an attacker can reliably force the client to crash, disabling application functionality and potentially triggering cascading failures in dependent services.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update MariaDB Connector/J to version 3.3.7, 3.4.5, or later, which includes the patch for this issue.
  • If upgrading cannot occur immediately, enforce TLS/SSL encryption for database connections to prevent man‑in‑the‑middle attackers from manipulating authentication packets.
  • Review network architecture to ensure only trusted database servers are reachable and monitor for anomalous authentication traffic patterns.

Generated by OpenCVE AI on November 2, 2026 at 13:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Mariadb
Mariadb mariadb-connector-j
Mariadb-corporation
Mariadb-corporation mariadb-connector-j
Vendors & Products Mariadb
Mariadb mariadb-connector-j
Mariadb-corporation
Mariadb-corporation mariadb-connector-j
Type Values Removed Values Added
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.
Title MariaDB Connector/J: Rogue server can crash the client during caching_sha2_password authentication
Weaknesses CWE-129
CWE-789
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-129

    Improper Validation of Array Index

  • CWE-130

    Improper Handling of Length Parameter Inconsistency

  • CWE-789

    Memory Allocation with Excessive Size Value

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 4:00 PM
Reserved
Oct 29, 2026, 6:50 PM
Status
Awaiting Analysis
Published
Oct 29, 2026, 9:17 PM
Modified
Oct 30, 2026, 5:07 PM
Severity
Moderate
Public date
Oct 29, 2026, 8:50 PM