Security incident · CVE-2026-119280
MariaDB Connector/J: XA recover() trusted server-supplied gtrid and bqual lengths
Published Oct 30, 2026 · catalog updated Oct 30, 2026 · MariaDB Connector/J: XA recover()
Last checked Oct 31, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-119280. EPSS is 0.31%. Act only if a listed version of MariaDB Connector/J: XA recover() is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (MariaDB Connector/J: XA recover()).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Low3.7
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.31%
- Remediation
- Version ranges on file
- Affected products
- Maven org.mariadb.jdbc:mariadb-java-client · maven org.mariadb.jdbc · maven org.mariadb.jdbc:mariadb-java-client
## Summary in MariaDB Connector/J trusted the and columns returned by to allocate and split each Xid. ## Details and built each of the recovery list by allocating and and copying from the column, without validating the lengths against the XA specification bounds ( , ) or the actual payload. Negative or oversized lengths, or lengths that do not fit the data, ended in large allocations or unchecked exceptions ( , ) during recovery. The fix validates the lengths before any allocation or copy and reports an invalid row as an ( ). ## 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. ## Credit Reported by fg0x0
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Maven org.mariadb.jdbc:mariadb-java-client3.0.0 → 3.3.7
- Maven org.mariadb.jdbc:mariadb-java-client3.4.0 → 3.4.5
- Maven org.mariadb.jdbc:mariadb-java-client3.5.0 → 3.5.11
- maven org.mariadb.jdbcversion unspecified
- maven org.mariadb.jdbc:mariadb-java-client>= 3.0.0, < 3.3.7
- maven org.mariadb.jdbc:mariadb-java-client>= 3.4.0, < 3.4.5
- maven org.mariadb.jdbc:mariadb-java-client>= 3.5.0, < 3.5.11
How to fix CVE-2026-119280
Upgrade
CVE-2026-119280 lists a fix boundary at 3.3.7. Compare the installed build with that boundary before you change production.
Version check
Affected < 3.3.7
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-119280. EPSS is 0.31%. Act only if a listed version of MariaDB Connector/J: XA recover() is installed.
Which versions are affected?
Compare what you have installed with 3.0.0 → 3.3.7, 3.4.0 → 3.4.5, 3.5.0 → 3.5.11, >= 3.0.0, < 3.3.7, >= 3.4.0, < 3.4.5, >= 3.5.0, < 3.5.11. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-20: Improper Input Validation; CWE-789. EPSS 0.31%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 30, 2026 · GitHub Advisory Database
Detected
## Summary in MariaDB Connector/J trusted the and columns returned by to allocate and split each Xid. ## Details and built each of the recovery list by allocating and and copying from the column, without validating the lengths against the XA specification bounds ( , ) or the actual payload. Negative or oversized lengths, or lengths that do not fit the data, ended in large allocations or unchecked
Oct 30, 2026 · GitHub Advisory Database
Fix available
org.mariadb.jdbc:mariadb-java-client fixed in 3.3.7; org.mariadb.jdbc:mariadb-java-client fixed in 3.4.5; org.mariadb.jdbc:mariadb-java-client fixed in 3.5.11
Oct 30, 2026 · GitHub Advisory Database
Fix available
org.mariadb.jdbc:mariadb-java-client fixed in 3.3.7
Oct 30, 2026 · GitHub Advisory Database
Fix available
org.mariadb.jdbc:mariadb-java-client fixed in 3.4.5
Oct 30, 2026 · GitHub Advisory Database
Fix available
org.mariadb.jdbc:mariadb-java-client fixed in 3.5.11
Oct 30, 2026 · GitHub Advisory Database
Updated
## Summary in MariaDB Connector/J trusted the and columns returned by to allocate and split each Xid. ## Details and built each of the recovery list by allocating and and copying from the column, without validating the lengths against the XA specification bounds ( , ) or the actual payload. Negative or oversized lengths, or lengths that do not fit the data, ended in large allocations or unchecked
Sources
- CVE.orgVulnerability recordCVE-2026-119280
Official CVE identifier
cve.org - GitHub Advisory DatabasePackage advisoryGHSA-4jq2-8v3c-97w8
MariaDB Connector/J: XA recover() trusted server-supplied gtrid and bqual lengths
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-119280
XAResource.recover() in MariaDB Connector/J trusted the gtrid_length and bqual_length columns returned by XA RECOVER to allocate and split each Xid.
advisories.gitlab.com - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-4jq2-8v3c-97w8
MariaDB Connector/J: XA recover() trusted server-supplied gtrid and bqual lengths
osv.dev
References
Freshness
Last verified in this catalog Oct 31, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgOct 31, 2026
- GitLab Advisory DatabaseOct 31, 2026
- GitHub Advisory DatabaseOct 31, 2026
- OpenSSF OSV / OSV ScannerOct 31, 2026