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.
Published: 2026-10-29
Score: 5.9 Medium
EPSS: < 1% Very Low
KEV: No
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 02 Nov 2026 12:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-130
References
Metrics threat_severity

None

 threat_severity

Moderate

Fri, 30 Oct 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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

Thu, 29 Oct 2026 22:45:00 +0000

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

Thu, 29 Oct 2026 21:00:00 +0000

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'}

Subscriptions

Mariadb Mariadb-connector-j
Mariadb-corporation Mariadb-connector-j
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-30T16:00:11.050Z

Reserved: 2026-10-29T18:50:28.064Z

Link: CVE-2026-119278

cve-icon Vulnrichment

Updated: 2026-10-30T15:20:42.642Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-29T21:17:21.237

Modified: 2026-10-30T17:07:53.700

Link: CVE-2026-119278

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-29T20:50:35Z

Links: CVE-2026-119278 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-29T22:45:03Z

Weaknesses
  • CWE-129

    Improper Validation of Array Index

  • CWE-130

    Improper Handling of Length Parameter Inconsistency

  • CWE-789

    Memory Allocation with Excessive Size Value