CVE-2026-119277: MariaDB Connector/J: Rogue server can make the client read past the packet through server-declared lengths

Published Oct 29, 2026
·
Updated

MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, decoders for OK packet session-state blocks, column definition packets, text row data, or binary row data used server-declared lengths without confirming that the requested bytes remained in the receive buffer. The decoders could position reads, create sub-buffers, or decode strings beyond the packet boundary. A malicious or compromised server, or a machine-in-the-middle attacker, could trigger unchecked ArrayIndexOutOfBoundsException or IllegalArgumentException failures inside JDBC calls and terminate connection handling. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.

Affected Software

10 affected components
debian/mariadb-connector-java*
debian/mariadb-connector-java*
debian/mariadb-connector-java*
debian/mariadb-connector-java<=2.7.6-1, <=3.5.10-1
ubuntu/mariadb-connector-java*
ubuntu/mariadb-connector-java*
ubuntu/mariadb-connector-java*
ubuntu/mariadb-connector-java*
ubuntu/mariadb-connector-java*
ubuntu/mariadb-connector-java*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade MariaDB Connector/J to a version that resolves this vulnerability.

    Fixed in 3.3.7
  2. Upgrade

    Upgrade MariaDB Connector/J to a version that resolves this vulnerability.

    Fixed in 3.4.5
  3. Upgrade

    Upgrade MariaDB Connector/J to a version that resolves this vulnerability.

    Fixed in 3.5.11

Event History

Oct 29, 2026
CVE Published
via MITRE·08:49 PM
Data Sourced
via MITRE·08:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·09:17 PM
Affected Software

Frequently Asked Questions

1

Which deployments are realistically exposed?

Java applications using MariaDB Connector/J versions affected by this issue are exposed when they connect to a malicious or compromised database server, or when an attacker can act as a machine in the middle of the database connection.

2

What does an attacker need to cause an impact?

The attacker must be able to supply crafted database protocol packets, either by controlling or compromising the server or by intercepting and modifying traffic between the application and the server. No application-side privileges or user interaction are required.

3

How can I identify potentially affected clients?

Identify applications using MariaDB Connector/J and check whether they run a version before 3.3.7, 3.4.5, or 3.5.11 in the applicable release line. Runtime symptoms may include unchecked ArrayIndexOutOfBoundsException or IllegalArgumentException failures during JDBC connection handling.

4

Which versions contain the fix?

The issue is fixed in MariaDB Connector/J 3.3.7, 3.4.5, and 3.5.11.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203