CVE-2026-119277

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-113384 (ENISA EUVD)Source: ENISA EUVD

5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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, decoders for OK packet session-state blocks, column definition packets, text row data, or binary row data used server-declared lengths without confirming that the requested bytes remained in the receive buffer. The decoders could position reads, create sub-buffers, or decode strings beyond the packet boundary. A malicious or compromised server, or a machine-in-the-middle attacker, could trigger unchecked ArrayIndexOutOfBoundsException or IllegalArgumentException failures inside JDBC calls and terminate connection handling. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-03). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 29, 2026

Last Modified

November 4, 2026

Advisory Details (7)

Auto-updated Oct 29, 2026
Patch available. Sources: github_release, github, github_commit.
GitHub advisoryMentions a patch (unverified)

Rogue server can make the client read past the packet through server-declared lengths · Advisory · mariadb-corporation/mariadb-connector-j · GitHub

https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-wfxr-v78w-p49r
GitHub release Patch Available

MariaDB Connector/Java 3.5.11

Patch available: mariadb-corporation/mariadb-connector-j 3.5.11

https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.11
GitHub release Patch Available

MariaDB Connector/Java 3.4.5

Patch available: mariadb-corporation/mariadb-connector-j 3.4.5

https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.4.5
GitHub release Patch Available

MariaDB Connector/Java 3.3.7

Patch available: mariadb-corporation/mariadb-connector-j 3.3.7

https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.3.7
GitHub commit Patch Available

commit ea8c7b6537e5 (mariadb-corporation/mariadb-connector-j)

Patch available: mariadb-corporation/mariadb-connector-j 3.4.5 (contains commit ea8c7b6537e5)

https://github.com/mariadb-corporation/mariadb-connector-j/commit/ea8c7b6537e50053444188a9a3fd9cae99550f56
GitHub commit Patch Available

commit 52538206298d (mariadb-corporation/mariadb-connector-j)

Patch available: mariadb-corporation/mariadb-connector-j 3.5.11 (contains commit 52538206298d)

https://github.com/mariadb-corporation/mariadb-connector-j/commit/52538206298db39062ad67939f1446b767cacde4
GitHub commit Patch Available

commit 49c92adfcf81 (mariadb-corporation/mariadb-connector-j)

Patch available: mariadb-corporation/mariadb-connector-j 3.3.7 (contains commit 49c92adfcf81)

https://github.com/mariadb-corporation/mariadb-connector-j/commit/49c92adfcf816853e324031ba9762a69444cfd12

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb-connector-java2.7.15-1, 2.7.6-1, 3.5.10-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb-connector-java2.7.15-1, 2.7.6-1, 3.5.10-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb-connector-java2.7.15-1, 2.7.6-1, 3.5.10-1
  • every version on: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 17× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  7. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  8. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-11-04 02:27 UTCEchelonGraph re-scored
  12. 2026-11-04 01:51 UTCEchelonGraph re-scored
  13. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-10-30 17:27 UTCEchelonGraph re-scored
  18. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-29 21:27 UTCEchelonGraph re-scored
  20. 2026-10-29 21:02 UTCENISA EUVD ID recordedEUVD-2026-113384 · Source: ENISA EUVD
  21. 2026-10-29 20:52 UTCEchelonGraph re-scoredFirst assessed: 5.9 MEDIUM
  22. 2026-10-29 20:51 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-119277?
CVE-2026-119277 is a medium-severity vulnerability; its CVE record was published on October 29, 2026. 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, decoders for OK packet session-state blocks, column definition packets, text row data, or binary row data used server-declared lengths without confirming…
When was the CVE record for CVE-2026-119277 published?
The CVE record for CVE-2026-119277 was published on October 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 4, 2026; the record at its source may have been updated since.
Is CVE-2026-119277 actively exploited?
CVE-2026-119277 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119277?
CVE-2026-119277 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119277?
A fix for CVE-2026-119277 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-119277

Explore →

Is Your Infrastructure Affected by CVE-2026-119277?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs