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

Source: https://junglewise.ai/threats/cve-2026-119280-mariadb-connector-j-is-used-to-connect-applications-developed-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-29  
License: CC BY 4.0 with a link back

CVE-2026-119280 · Severity: low · CVSS 3.7 · Published 2026-10-29

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.

Technologies: [org.mariadb.jdbc:mariadb-java-client (Maven)](https://junglewise.ai/threats/technologies/org-mariadb-jdbc-mariadb-java-client). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2026-119280 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-119280 being exploited in the wild.

**How severe is CVE-2026-119280?** Low severity, with a CVSS score of 3.7, published 29 October 2026.

**Which products and versions are affected?** org.mariadb.jdbc:mariadb-java-client (Maven) >= 3.0.0, < 3.3.7, ECOSYSTEM:introduced=3.0.0,fixed=3.3.7.

**Is there a fix for CVE-2026-119280?** Yes. org.mariadb.jdbc:mariadb-java-client (Maven): upgrade to 3.3.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-119280?** Check whether you run org.mariadb.jdbc:mariadb-java-client (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.mariadb.jdbc:mariadb-java-client (Maven): upgrade to 3.3.7 or later

  ```sh
  # set org.mariadb.jdbc:mariadb-java-client to 3.3.7 in your pom.xml or build.gradle
  ```


## Affected products

- org.mariadb.jdbc:mariadb-java-client (Maven) >= 3.0.0, < 3.3.7, ECOSYSTEM:introduced=3.0.0,fixed=3.3.7

## Identifiers

- CVE-2026-119280
- GHSA-4jq2-8v3c-97w8

## Related threats

- [MariaDB Connector/J character set validation bypass](https://junglewise.ai/threats/cve-2026-119281-mariadb-connector-j-is-used-to-connect-applications-developed-in)
- [MariaDB Connector/J integer overflow in length encoding](https://junglewise.ai/threats/cve-2026-119279-mariadb-connector-j-is-used-to-connect-applications-developed-in)
- [MariaDB Connector/J heap allocation denial of service](https://junglewise.ai/threats/cve-2026-119276-mariadb-connector-j-is-used-to-connect-applications-developed-in)
- [MariaDB Connector/J LOAD DATA LOCAL INFILE bypass in metadata queries](https://junglewise.ai/threats/cve-2026-119210-mariadb-connector-j-is-used-to-connect-applications-developed-in)
- [MariaDB Connector/J allowLocalInfile bypass in LOCAL INFILE processing](https://junglewise.ai/threats/cve-2026-61700-mariadb-connector-j-allowlocalinfile-bypass-in-local-infile)