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.11, the MariaDbPoolConnection.recover() and MariaDbPoolPinnedConnection.recover() implementations trusted the gtrid_length and bqual_length columns returned by XA RECOVER. The methods allocated and split Xid byte arrays without validating the lengths against Xid.MAXGTRIDSIZE, Xid.MAXBQUALSIZE, or the actual data payload. A malicious or compromised server, or a machine-in-the-middle attacker, could cause large allocations, NegativeArraySizeException, or ArrayIndexOutOfBoundsException during XA recovery. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11. | |
| Title | MariaDB Connector/J : XA recover() trusted server-supplied gtrid and bqual lengths | |
| Weaknesses | CWE-20 CWE-789 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-29T20:55:50.101Z
Reserved: 2026-10-29T18:50:28.064Z
Link: CVE-2026-119280
No data.
Status : Received
Published: 2026-10-29T21:17:21.553
Modified: 2026-10-29T21:17:21.553
Link: CVE-2026-119280
No data.
OpenCVE Enrichment
Updated: 2026-10-29T22:30:13Z