LowCVE-2026-119280

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

    Published Last modified Sources: BSI, OSV, Hersteller, CVE.org

    What is affected, what to do

    Update MariaDB Java Connector to version 3.5.11, org.mariadb.jdbc:mariadb-java-client to version 3.4.5.

    Affected
    • Mariadb-corporation Mariadb-connector-j gte 3.0.0, < 3.3.7..*

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    3.7

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    3.7

    CVSS v3

    Severity Low on the scale from 0 to 10.

    Source: BSI, OSV, Hersteller, CVE.org

    0.3 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 23.4

    Show all metrics
    Severity
    Low
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    52.88 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    3.7 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    3.7
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.3 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    23.4
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 30 October 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-20, CWE-789

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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 allocations. Exploitation requires control of the server side of the connection.

    Credit

    Reported by fg0x0

    Source: BSI CSAF, BSI WID Portal, OSV (Open Source Vulnerabilities), GitHub Security Advisories, cvelistv5, NVD (NIST)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    mariadb-corporationmariadb-connector-j
    • ≥ 3.0.0, < 3.3.7
    • —
    MariaDBMariaDB Java Connector
    • < 3.5.11
    • < 3.4.5
    • < 3.3.7
    • 3.5.11
    • 3.4.5
    • 3.3.7
    mavenorg.mariadb.jdbc:mariadb-java-client
    • 3.5.1
    • 3.3.1
    • 3.0.4
    • 3.3.2
    • 3.5.3
    • 3.1.0
    • >= 3.4.0, < 3.4.5
    • 3.5.2
    • 3.0.1-beta
    • 3.5.4
    • 3.5.9
    • 3.4.1
    • 3.0.6
    • 3.5.7
    • 3.4.2
    • 3.0.0
    • 3.0.3
    • 3.5.5
    • 3.4.0
    • >= 3.0.0, < 3.3.7
    • 3.0.7
    • 3.4.3
    • 3.5.10
    • 3.3.4
    • 3.0.2-rc
    • 3.0.10
    • 3.0.8
    • 3.5.0
    • 3.4.4
    • 3.5.6
    • 3.1.1
    • 3.0.9
    • 3.3.6
    • 3.5.8
    • >= 3.5.0, < 3.5.11
    • 3.0.11
    • 3.1.2
    • 3.2.0
    • 3.3.3
    • 3.3.0
    • 3.1.3
    • 3.3.5
    • 3.0.5
    • 3.1.4
    • —
    • —
    • —
    • —
    • —
    • —
    • 3.4.5
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • 3.3.7
    • —
    • —
    • 3.4.5
    • 3.3.7
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • 3.5.11
    • —
    • —
    • —
    • —
    • —
    • —
    • 3.5.11
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-20Improper Input Validation

      Class

      The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

      Entry at MITRE CWE-20

    • CWE-789Memory Allocation with Excessive Size Value

      Variant

      The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

      Entry at MITRE CWE-789

    References & sources

    • github.commariadb-corporation/mariadb-connector-j/commit/280efcfb43900558…x_refsource_MISC, web
    • github.commariadb-corporation/mariadb-connector-j/commit/47aba5a23548b351…x_refsource_MISC, web
    • github.commariadb-corporation/mariadb-connector-j/commit/e9d767103bfd178e…x_refsource_MISC, web
    • github.commariadb-corporation/mariadb-connector-j/releases/tag/3.3.7x_refsource_MISC, web
    • github.commariadb-corporation/mariadb-connector-j/releases/tag/3.4.5x_refsource_MISC, web
    • github.commariadb-corporation/mariadb-connector-j/releases/tag/3.5.11x_refsource_MISC, web
    • github.commariadb-corporation/mariadb-connector-j/security/advisories/GHS…x_refsource_CONFIRM, web
    • NVD (NIST)vuln/detail/CVE-2026-119280advisory
    • github.commariadb-corporation/mariadb-connector-jpackage

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-119280","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-30T17:09:58.150194Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      CVSS V3.1: AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

      Weakness type: CWE-20, CWE-789

      Description added or changed

      Show 12 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
      Weakness type (CWE)added
      —
      CWE-20
      Weakness type (CWE)added
      —
      CWE-789
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/119xxx/CVE-2026-119280.json">CVE-2026-119280</a>
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/commit/280efcfb4390055858fa2dd12b722d85a6a13ab8
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/commit/47aba5a23548b35191865a428cc674316b95ee47
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/commit/e9d767103bfd178ed57caa4cb97bbfbf7e54da6b
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.3.7
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.4.5
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.11
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-4jq2-8v3c-97w8

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-119280
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-119280"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-119280.svg?lang=en" alt="CVE-2026-119280 – NEOSEC Intel" height="20"></a>