Security incident · CVE-2026-119279
MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated before being used as lengths
Published Oct 30, 2026 · catalog updated Oct 30, 2026 · MariaDB Connector/J: Length-encoded integers
Last checked Oct 31, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-119279. EPSS is 0.35%. Act only if a listed version of MariaDB Connector/J: Length-encoded integers is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (MariaDB Connector/J: Length-encoded integers).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium5.9
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.35%
- Remediation
- Version ranges on file
- Affected products
- Maven org.mariadb.jdbc:mariadb-java-client · maven org.mariadb.jdbc · maven org.mariadb.jdbc:mariadb-java-client
## Summary MariaDB Connector/J narrowed 8-byte length-encoded integers received from the server to without validation. A rogue or MitM server can send a value above whose truncation becomes a negative or arbitrary length. ## Details The protocol encodes lengths as length-encoded integers, whose 8-byte form the decoder ( and ) returned as . A value above therefore wrapped to a negative or unrelated , used afterwards as a length to size allocations or reads, which ended in , out-of-bounds exceptions or oversized allocations. The fix rejects any length-encoded value that does not fit a non-negative with an explicit error. ## Impact Availability only: a malicious or compromised server, or a MitM, can crash the client's connection handling with unchecked exceptions or drive oversized allocations. Exploitation requires control of the server side of the connection; no authentication bypass, confidentiality or integrity impact. ## Credit Reported by fg0x0
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Maven org.mariadb.jdbc:mariadb-java-client3.0.0 → 3.3.7
- Maven org.mariadb.jdbc:mariadb-java-client3.4.0 → 3.4.5
- Maven org.mariadb.jdbc:mariadb-java-client3.5.0 → 3.5.10
- maven org.mariadb.jdbcversion unspecified
- maven org.mariadb.jdbc:mariadb-java-client>= 3.0.0, < 3.3.7
- maven org.mariadb.jdbc:mariadb-java-client>= 3.4.0, < 3.4.5
- maven org.mariadb.jdbc:mariadb-java-client>= 3.5.0, < 3.5.10
How to fix CVE-2026-119279
Upgrade
CVE-2026-119279 lists a fix boundary at 3.3.7. Compare the installed build with that boundary before you change production.
Version check
Affected < 3.3.7
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-119279. EPSS is 0.35%. Act only if a listed version of MariaDB Connector/J: Length-encoded integers is installed.
Which versions are affected?
Compare what you have installed with 3.0.0 → 3.3.7, 3.4.0 → 3.4.5, 3.5.0 → 3.5.10, >= 3.0.0, < 3.3.7, >= 3.4.0, < 3.4.5, >= 3.5.0, < 3.5.10. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-130; CWE-190: Integer Overflow. EPSS 0.35%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 30, 2026 · GitHub Advisory Database
Detected
## Summary MariaDB Connector/J narrowed 8-byte length-encoded integers received from the server to without validation. A rogue or MitM server can send a value above whose truncation becomes a negative or arbitrary length. ## Details The protocol encodes lengths as length-encoded integers, whose 8-byte form the decoder ( and ) returned as . A value above therefore wrapped to a negative or unrelated
Oct 30, 2026 · GitHub Advisory Database
Fix available
org.mariadb.jdbc:mariadb-java-client fixed in 3.3.7; org.mariadb.jdbc:mariadb-java-client fixed in 3.4.5; org.mariadb.jdbc:mariadb-java-client fixed in 3.5.10
Oct 30, 2026 · GitHub Advisory Database
Fix available
org.mariadb.jdbc:mariadb-java-client fixed in 3.3.7
Oct 30, 2026 · GitHub Advisory Database
Fix available
org.mariadb.jdbc:mariadb-java-client fixed in 3.4.5
Oct 30, 2026 · GitHub Advisory Database
Fix available
org.mariadb.jdbc:mariadb-java-client fixed in 3.5.10
Oct 30, 2026 · GitHub Advisory Database
Updated
## Summary MariaDB Connector/J narrowed 8-byte length-encoded integers received from the server to without validation. A rogue or MitM server can send a value above whose truncation becomes a negative or arbitrary length. ## Details The protocol encodes lengths as length-encoded integers, whose 8-byte form the decoder ( and ) returned as . A value above therefore wrapped to a negative or unrelated
Sources
- CVE.orgVulnerability recordCVE-2026-119279
Official CVE identifier
cve.org - GitHub Advisory DatabasePackage advisoryGHSA-797x-p4mc-jwpm
MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated before being used as lengths
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-119279
MariaDB Connector/J narrowed 8-byte length-encoded integers received from the server to int without validation. A rogue or MitM server can send a value above Integer.MAX_VALUE whose truncation becomes a negative or arbitrary length.
advisories.gitlab.com - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-797x-p4mc-jwpm
MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated before being used as lengths
osv.dev
References
Freshness
Last verified in this catalog Oct 31, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgOct 31, 2026
- GitLab Advisory DatabaseOct 31, 2026
- GitHub Advisory DatabaseOct 31, 2026
- OpenSSF OSV / OSV ScannerOct 31, 2026