cve.bz

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

3.7 lowEPSS 0.4%Fix available

Low (3.7) in mariadb-corporation mariadb-connector-j. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.mariadb.jdbc:mariadb-java-client 3.3.7, 3.4.5, 3.5.11.

On this page
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.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.4% (up from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-789 Memory Allocation with Excessive Size Value
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-119280 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-119280?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-119280?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-119280 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
mariadb-corporation mariadb-connector-j>= 3.0.0, < 3.3.7
mariadb-corporation mariadb-connector-j>= 3.4.0, < 3.4.5
mariadb-corporation mariadb-connector-j>= 3.5.0, < 3.5.11

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4jq2-8v3c-97w8Mavenorg.mariadb.jdbc:mariadb-java-client>=3.0.0 <3.3.73.3.7
GHSA-4jq2-8v3c-97w8Mavenorg.mariadb.jdbc:mariadb-java-client>=3.4.0 <3.4.53.4.5
GHSA-4jq2-8v3c-97w8Mavenorg.mariadb.jdbc:mariadb-java-client>=3.5.0 <3.5.113.5.11

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14mariadb-connector-javano fix listedDEBIAN-CVE-2026-119280
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 3 moremariadb-connector-javano fix listedUBUNTU-CVE-2026-119280
openSUSETumbleweedmariadb-java-client3.5.11-1.1openSUSE-SU-2026:12401-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This vulnerability is rated as Low severity because successful exploitation requires an attacker to either control the upstream database server or perform an active machine-in-the-middle attack on the connection. The flaw is confined to distributed XA transaction recovery procedures when parsing responses from the database. As a result, the vulnerability cannot lead to compromise of sensitive data or unauthorized system access, restricting the impact entirely to client-side denial of service.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat build of Debezium 3mariadb-java-clientFix deferred
Red Hat Build of Keycloakmariadb-java-clientFix deferred
Red Hat Build of Keycloakrhbk/keycloak-rhel9Fix deferred
Red Hat build of Quarkusmariadb-java-clientAffected
Red Hat Enterprise Linux 10mariadb-java-clientFix deferred
Red Hat Enterprise Linux 8mariadb:10.3/mariadbFix deferred
Red Hat Enterprise Linux 8mariadb-devel:10.3/mariadbFix deferred
Red Hat Enterprise Linux 9mariadb-java-clientFix deferred
Red Hat Hardened Imagesmariadb10.11Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-trustyai-service-rhel9Fix deferred
Red Hat OpenStack Platform 13 (Queens)mariadbOut of support scope
Red Hat Satellite 6candlepinFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-119280.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON