Summary
MariaDB Connector/J: XA recover() trusted server-supplied gtrid and bqual lengths
XAResource.recover() in MariaDB Connector/J trusted the gtrid_length andbqual_length columns returned by XA RECOVER to allocate and split each Xid.
Details
MariaDbPoolConnection and MariaDbPoolPinnedConnection built each Xid of
the recovery list by allocating new byte[gtrid_length] andnew byte[bqual_length] and copying from the data column, without validating
the lengths against the XA specification bounds (Xid.MAXGTRIDSIZE,Xid.MAXBQUALSIZE) or the actual payload. Negative or oversized lengths, or
lengths that do not fit the data, ended in large allocations or unchecked
exceptions (NegativeArraySizeException, ArrayIndexOutOfBoundsException)
during recovery.
The fix validates the lengths before any allocation or copy and reports an
invalid row as an XAException (XAER_RMFAIL).
Credit
Reported by fg0x0
Impact
Availability only, and limited to applications running XA recovery: a malicious
or compromised server, or a MitM, can crash the recovery or drive large
allocations. Exploitation requires control of the server side of the connection.
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
CVE-2026-119280 has a CVSS score of 3.7 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.3.7, 3.4.5, 3.5.11); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.mariadb.jdbc:mariadb-java-client to 3.3.7 or later; org.mariadb.jdbc:mariadb-java-client to 3.4.5 or later; org.mariadb.jdbc:mariadb-java-client to 3.5.11 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-119280? CVE-2026-119280 is a low-severity improper input validation vulnerability in org.mariadb.jdbc:mariadb-java-client (maven), affecting versions >= 3.0.0, < 3.3.7. It is fixed in 3.3.7, 3.4.5, 3.5.11. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- How severe is CVE-2026-119280? CVE-2026-119280 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.mariadb.jdbc:mariadb-java-client are affected by CVE-2026-119280? org.mariadb.jdbc:mariadb-java-client (maven) versions >= 3.0.0, < 3.3.7 is affected.
- Is there a fix for CVE-2026-119280? Yes. CVE-2026-119280 is fixed in 3.3.7, 3.4.5, 3.5.11. Upgrade to this version or later.
- Is CVE-2026-119280 exploitable, and should I be worried? Whether CVE-2026-119280 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-119280 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-119280?
- Upgrade
org.mariadb.jdbc:mariadb-java-clientto 3.3.7 or later - Upgrade
org.mariadb.jdbc:mariadb-java-clientto 3.4.5 or later - Upgrade
org.mariadb.jdbc:mariadb-java-clientto 3.5.11 or later
- Upgrade