MariaDB Connector/J: XA recover() trusted server-supplied gtrid and bqual lengths
CVE-2026-119280GHSA-4jq2-8v3c-97w8
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.mariadb.jdbc:mariadb-java-client 3.5.11, 3.4.5, 3.3.7), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.mariadb.jdbc:mariadb-java-client
- Affected
- >= 3.0.0, < 3.3.7>= 3.4.0, < 3.4.5>= 3.5.0, < 3.5.11
- Fixed in
- 3.5.11, 3.3.7, 3.4.5
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-4jq2-8v3c-97w8 lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=3.0.0 =3.4.0 =3.5.0 <3.5.11
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-4jq2-8v3c-97w8 lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=3.0.0 =3.4.0 =3.5.0 <3.5.11 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
- EPSS
- CVE-2026-119280: 0.31% estimated exploitation activity in the next 30 days; percentile 23.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary `XAResource.recover()` in MariaDB Connector/J trusted the `gtrid_length` and `bqual_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]` and `new 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`).
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-4jq2-8v3c-97w8
- Revision 1 · created ·
Published from ghsa record GHSA-4jq2-8v3c-97w8
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-119280 Advisory: MariaDB Connector/J: XA recover() trusted server-supplied gtrid and bqual lengths IDs: CVE-2026-119280, GHSA-4jq2-8v3c-97w8 Record: https://patchnext.com/advisories/cve-2026-119280 (revision 2, source checked 31 Oct 2026, 07:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 3.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.mariadb.jdbc:mariadb-java-client 3.5.11, 3.4.5, 3.3.7. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.mariadb.jdbc:mariadb-java-client: affected >= 3.0.0, < 3.3.7; >= 3.4.0, < 3.4.5; >= 3.5.0, < 3.5.11; fixed in 3.5.11, 3.3.7, 3.4.5 ## Suggested inspection (read-only) - Maven org.mariadb.jdbc:mariadb-java-client: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.mariadb.jdbc:mariadb-java-client. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-4jq2-8v3c-97w8 (GitHub-reviewed advisory GHSA-4jq2-8v3c-97w8 lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=3.0.0 =3.4.0 =3.5.0 <3.5.11) - Verified: https://osv.dev/vulnerability/GHSA-4jq2-8v3c-97w8 (OSV record GHSA-4jq2-8v3c-97w8 lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=3.0.0 =3.4.0 =3.5.0 <3.5.11 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…