Improper Handling of Length Parameter Inconsistency Affecting mariadb-connector-java package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.35% (29th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-MARIADBCONNECTORJAVA-21884757
  • published30 Oct 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

NewCVE-2026-119279  (opens in a new tab)
CWE-130  (opens in a new tab)
CWE-190  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest mariadb-connector-java.

NVD Description

Note: Versions mentioned in the description apply only to the upstream mariadb-connector-java package and not the mariadb-connector-java package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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.10, the ReadableByteBuf.readLength() and ReadableByteBuf.readIntLengthEncodedNotNull() methods narrowed the protocol's unsigned 8-byte length-encoded integer to a Java int without checking that the value fit a non-negative integer. Values above Integer.MAX_VALUE could wrap to a negative or unrelated length that downstream allocation and read paths used. A malicious or compromised server, or a machine-in-the-middle attacker, could trigger NegativeArraySizeException, out-of-bounds failures, or oversized allocation behavior in client connection handling. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.10.