CVE-2026-119280

MariaDB Connector/J : XA recover() trusted server-supplied gtrid and bqual lengths

Published Oct 29, 2026 CVSS 3.1 · 3.7 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

MariaDB Connector/J used in Java applications performs XA recovery by trusting the gtrid_length and bqual_length fields supplied by the database during the XA RECOVER command. Because the driver does not validate these lengths against Xid.MAXGTRIDSIZE, Xid.MAXBQUALSIZE, or the actual payload, a malicious or compromised server or a man‑in‑the‑middle attacker can trigger large memory allocations, NegativeArraySizeException, or ArrayIndexOutOfBoundsException during recovery, causing the application to fail or crash. This flaw does not provide code execution or privilege escalation, but it can disrupt database transactions and lead to service interruption.

Affected Systems

The vulnerability affects MariaDB Connector/J from version 3.0.0 through 3.3.7, 3.4.5, and 3.5.11. These releases are distributed by MariaDB Corporation. Any Java application using these driver versions and performing XA recovery is impacted.

Risk and Exploitability

The CVSS score for this issue is 3.7, indicating low severity. No EPSS score is available, and the flaw is not listed in the CISA KEV catalog. The likely attack vector requires an attacker to control or tamper with the database server or to intercept and alter the network traffic between the application and the database. Thus, while exploitation is possible, it is limited to environments where the attacker can influence the server responses or perform a man‑in‑the‑middle attack. The risk is moderate, making patching the recommended course of action.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade MariaDB Connector/J to version 3.3.7 or later (3.4.5, 3.5.11) to obtain the fix.
  • If an upgrade cannot occur immediately, configure the application to disable XA recovery or avoid using XA features until the driver is patched, thereby preventing the failure axis during recovery.
  • Ensure the database connection uses a trusted, encrypted channel and perform regular audit of XA recovery logs to detect any remaining exceptions or recovery failures.

Generated by OpenCVE AI on October 30, 2026 at 13:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-4jq2-8v3c-97w8 MariaDB Connector/J: XA recover() trusted server-supplied gtrid and bqual lengths
History
Type Values Removed Values Added
Metrics ssvc

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

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

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-130

    Improper Handling of Length Parameter Inconsistency

  • CWE-20

    Improper Input Validation

  • CWE-789

    Memory Allocation with Excessive Size Value

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 5:10 PM
Reserved
Oct 29, 2026, 6:50 PM
Status
Awaiting Analysis
Published
Oct 29, 2026, 9:17 PM
Modified
Oct 30, 2026, 5:18 PM
Severity
Low
Public date
Oct 29, 2026, 8:55 PM