MediumCVE-2026-119276

    Mariadb-corporation Mariadb-connector-j: Memory Allocation with Excessive Size Value (CVE-2026-119276)

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

    What is affected, what to do

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

    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

    5.9

    Priority

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

    Source: Vendor (CNA), CVSS v3

    5.9

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: OSV, CVE.org, BSI, Hersteller

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 28.8

    Show all metrics
    Severity
    Medium
    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
    66.12 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
    5.9 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
    5.9
    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.4 %
    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
    28.8
    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-130, 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

    MariaDB Connector/J sized heap allocations from lengths declared by the server in OK packets before checking that those lengths fit in the packet. A rogue or MitM server can make the client allocate megabytes from a packet of a few bytes.

    Details

    When CLIENT_SESSION_TRACK is negotiated (the default), an OK packet carries an info field followed by session-state blocks, each tracked variable being sent as a length-encoded name and value. OkPacket.parse() and parseWithInfo() allocated new byte[len] for the info field, the variable name and the value with the server-declared len, then copied the packet data into it. The copy failed with an ArrayIndexOutOfBoundsException when the packet was shorter, but only after the allocation had taken place.

    A server-declared length of 8 MiB in an 18-byte packet was enough to trigger an 8 MiB allocation; the integer-range validation of length-encoded values does not help, since such lengths are valid positive integers.

    The fix validates every server-declared length against the remaining packet bytes before any allocation (ReadableByteBuf.checkLength() and a bounded readBytes(int)), and stops reading the session state at the first inconsistent entry.

    Impact

    Availability only: a malicious or compromised server, or a MitM, can drive attacker-controlled heap allocations on every OK packet, creating GC pressure up to OutOfMemoryError in the client application. Exploitation requires control of the server side of the connection; no authentication bypass, confidentiality or integrity impact.

    Credit

    Reported by fg0x0

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

    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.3.0
    • 3.3.4
    • 3.0.6
    • 3.4.3
    • 3.4.1
    • 3.5.6
    • 3.3.1
    • 3.0.3
    • 3.5.1
    • 3.0.9
    • >= 3.0.0, < 3.3.7
    • 3.3.5
    • 3.0.0
    • 3.0.7
    • 3.0.4
    • 3.4.4
    • 3.5.0
    • 3.3.3
    • 3.4.0
    • 3.1.4
    • 3.1.3
    • 3.3.6
    • 3.4.2
    • 3.5.10
    • 3.0.8
    • 3.0.11
    • 3.5.8
    • 3.5.2
    • 3.2.0
    • 3.1.0
    • 3.1.1
    • 3.0.5
    • 3.0.2-rc
    • 3.5.9
    • 3.1.2
    • 3.3.2
    • >= 3.4.0, < 3.4.5
    • 3.5.3
    • 3.5.5
    • 3.5.7
    • >= 3.5.0, < 3.5.11
    • 3.5.4
    • 3.0.10
    • 3.0.1-beta
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • 3.3.7
    • —
    • 3.3.7
    • —
    • —
    • —
    • 3.5.11
    • —
    • 3.4.5
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • 3.4.5
    • —
    • —
    • —
    • 3.5.11
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-130Improper Handling of Length Parameter Inconsistency

      Base

      The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.

      Entry at MITRE CWE-130

    • 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/b9e1ee8d9b4d820d…x_refsource_MISC, web
    • github.commariadb-corporation/mariadb-connector-j/commit/beb445fcf9294113…x_refsource_MISC, web
    • github.commariadb-corporation/mariadb-connector-j/commit/ea8c7b6537e50053…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-119276advisory
    • 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-119276","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-30T17:11:37.642004Z"}

      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:H

      Weakness type: CWE-130, 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, when CLIENT_SESSION_TRACK was negotiated, the OkPacket.parse() and OkPacket.parseWithInfo() paths allocated byte arrays using server-declared lengths for the OK packet info field and session-state variable names and values before confirming that the bytes remained in the packet. A malicious or compromised server, or a machine-in-the-middle attacker, could send a small OK packet declaring a much larger length and repeatedly force attacker-controlled heap allocations before the subsequent copy failed. This could create garbage-collection pressure or an OutOfMemoryError in the client application. 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:H
      Weakness type (CWE)added
      —
      CWE-130
      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-119276.json">CVE-2026-119276</a>
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/commit/b9e1ee8d9b4d820d70719504cdfd5c97f1aede5f
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/commit/beb445fcf9294113878fc05ac77f0efdf0596ac6
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/commit/ea8c7b6537e50053444188a9a3fd9cae99550f56
      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-h599-m3w5-9m7x

      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-119276
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-119276"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-119276.svg?lang=en" alt="CVE-2026-119276 – NEOSEC Intel" height="20"></a>