Skip to main content
VulnerabilityPublished

CVE-2026-119280: mariadb-connector-j · Improper Input Validation

Affects mariadb-connector-jSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.7 Low · fixed in 3.5.11 : update mariadb-connector-j when convenient.

Data as of 29 Oct 2026, 22:01 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.13.7
Patch
Available – fixed in 3.5.11, 3.4.5, 3.3.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade mariadb-connector-j to 3.5.11, 3.4.5 or 3.3.7.

Affected software

ProductAffectedFixed in
mariadb-corporationmariadb-connector-jAffected
  • >=3.5.0 <3.5.11
Fixed in
  • 3.5.11
mariadb-corporationmariadb-connector-jAffected
  • >=3.4.0 <3.4.5
Fixed in
  • 3.4.5
mariadb-corporationmariadb-connector-jAffected
  • >=3.0.0 <3.3.7
Fixed in
  • 3.3.7

AI-suggested

Upgrade MariaDB Connector/J to version 3.3.7, 3.4.5, or 3.5.11 or later where this issue is fixed. No other mitigation is required as the vulnerability is addressed by these official fixes.

Description

MariaDB Connector/J versions from 3.0.0 up to but not including 3.3.7, 3.4.5, and 3.5.11 contain an improper input validation vulnerability in the XA recovery process. The recover() methods trust length values from the XA RECOVER command without validating them against maximum allowed sizes, potentially causing exceptions or large memory allocations. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.

References

Community reviews

Loading reviews…