Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
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, 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. | |
| Title | MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated before being used as lengths | |
| Weaknesses | CWE-130 CWE-190 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-29T20:52:22.903Z
Reserved: 2026-10-29T18:50:28.064Z
Link: CVE-2026-119279
No data.
Status : Received
Published: 2026-10-29T21:17:21.387
Modified: 2026-10-29T21:17:21.387
Link: CVE-2026-119279
No data.
OpenCVE Enrichment
Updated: 2026-10-29T22:30:12Z