CVE-2026-119210

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence

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

Score 5.9 from GitHub Security Advisory (severity: MODERATE) published 2026-10-30. A secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-113382 (ENISA EUVD) · GHSA-fhx5-2xqw-2cgm (GitHub Security Advisories)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.3%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, the ClientMessage.validateLocalFileName() check used a regular expression that could match LOAD DATA LOCAL INFILE text inside quoted identifiers, string literals, or comments instead of requiring a real statement. A malicious or compromised server, or a machine-in-the-middle attacker, could return crafted database or table identifiers that the connector reused in metadata or updatable-result queries, then answer with a LOCAL INFILE request for a client file. With allowLocalInfile enabled, this caused the connector to stream any readable client-host file named by the crafted text, including through DatabaseMetaData.getImportedKeys(), DatabaseMetaData.getExportedKeys(), or ResultSet.updateRow() paths. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.

CVSS v3
5.9
EG Score
5.9MEDIUMhigh 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.3% × 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.3%
EPSS %ILE
23rd
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.GitHub Security Advisory CVSS
EG Likelihood
0.3% 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 3, 2026

Advisory Details (7)

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

LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a malicious server read client files · Advisory · mariadb-corporation/mariadb-connector-j · GitHub

https://github.com/mariadb-corporation/mariadb-connector-j/security/advisories/GHSA-fhx5-2xqw-2cgm
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 a4891f877f1c (mariadb-corporation/mariadb-connector-j)

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

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

commit 5812e0ca7574 (mariadb-corporation/mariadb-connector-j)

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

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

commit 4d2f80023999 (mariadb-corporation/mariadb-connector-j)

Patch available: mariadb-corporation/mariadb-connector-j 3.3.7 (contains commit 4d2f80023999)

https://github.com/mariadb-corporation/mariadb-connector-j/commit/4d2f8002399949ed7f138e9c0b75b69229538120

Vendor Advisories for CVE-2026-119210(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.mariadb.jdbc:mariadb-java-client @ 3.3.7 (fixes >= 3.0.0, < 3.3.7)—ghsa
mavenorg.mariadb.jdbc:mariadb-java-client @ 3.4.5 (fixes >= 3.4.0, < 3.4.5)—ghsa
mavenorg.mariadb.jdbc:mariadb-java-client @ 3.5.11 (fixes >= 3.5.0, < 3.5.11)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 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
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.mariadb.jdbc:mariadb-java-client3.5.0 ... 3.5.9 (11 versions)
  • 3.0.0 up to 3.3.7: fixed in 3.3.7
  • 3.4.0 up to 3.4.5: fixed in 3.4.5
  • 3.5.0 up to 3.5.11: fixed in 3.5.11
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 18× 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-12 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-11-03 17:27 UTCEchelonGraph re-scored
  11. 2026-11-03 17:27 UTCGHSA enrichmentGHSA-fhx5-2xqw-2cgm · GitHub severity MODERATE · GitHub CVSS 5.9
  12. 2026-11-03 16:57 UTCEchelonGraph re-scored
  13. 2026-11-03 16:57 UTCGHSA enrichmentGHSA-fhx5-2xqw-2cgm · GitHub severity MODERATE · GitHub CVSS 5.9
  14. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  15. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  18. 2026-10-30 17:27 UTCEchelonGraph re-scored
  19. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-10-29 21:28 UTCEchelonGraph re-scored
  21. 2026-10-29 21:02 UTCENISA EUVD ID recordedEUVD-2026-113382 · Source: ENISA EUVD
  22. 2026-10-29 20:52 UTCEchelonGraph re-scoredFirst assessed: 5.9 MEDIUM
  23. 2026-10-29 20:51 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-119210?
CVE-2026-119210 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, the ClientMessage.validateLocalFileName() check used a regular expression that could match LOAD DATA LOCAL INFILE text inside quoted identifiers, string…
When was the CVE record for CVE-2026-119210 published?
The CVE record for CVE-2026-119210 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 3, 2026; the record at its source may have been updated since.
Is CVE-2026-119210 actively exploited?
CVE-2026-119210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119210?
CVE-2026-119210 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-119210?
A fix for CVE-2026-119210 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-119210 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-119210?

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

Book a Demo →Browse All CVEs