MediumCVE-2026-119210

    Mariadb-corporation Mariadb-connector-j: External Control of File Name or Path (CVE-2026-119210)

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

    What is affected, what to do

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

    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: BSI, OSV, Hersteller, CVE.org

    0.3 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 23.1

    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
    63.76 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.3 %
    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
    23.1
    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
    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-20, CWE-73

    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 checked a server's LOAD DATA LOCAL INFILE file request by searching the text of the command it had sent for LOAD DATA LOCAL INFILE '<file>'. The search also matched inside quoted identifiers, string literals and comments, so text returned by the server and re-used in a later query could satisfy it. A rogue or MitM server can read any file the client JVM can read.

    Details

    When a server answers a command with a LOCAL INFILE request (0xFB packet), the connector opens the named file on the client host and streams it to the server, after verifying that the file corresponds to a LOAD DATA LOCAL INFILE of the command it sent (ClientMessage.validateLocalFileName()). That verification was a regular expression whose prefix accepted any character, so it answered "does the text appear anywhere in the SQL", including inside a backtick-quoted identifier.

    Several driver paths put identifiers returned by the server straight back into their next query: DatabaseMetaData.getImportedKeys() and getExportedKeys() re-use database and table names from SHOW DATABASES, SHOW TABLES and the REFERENCES clause of SHOW CREATE TABLE output, and updatable result sets build their UPDATE and refresh SELECT from the schema and table names of the column definition packets. A server returning an identifier such as LOAD DATA LOCAL INFILE '/etc/passwd' makes the connector send SHOW CREATE TABLE `LOAD DATA LOCAL INFILE '/etc/passwd'`.`accounts` ; the server answers it with a LOCAL INFILE request for /etc/passwd, the check passes, and the file content is sent. On the getImportedKeys() path the resulting error is swallowed and the application observes nothing. The same applies to an application that interpolates identifiers obtained from the server into its own queries.

    The fix parses the command instead of searching it: string literals, quoted identifiers and comments are skipped, statements are split on ;, and only a LOAD DATA|XML [LOW_PRIORITY|CONCURRENT] LOCAL INFILE found at the start of a statement is considered, its file literal or bound parameter being compared exactly to the requested file.

    Impact

    Confidentiality: a malicious or compromised server, or a MitM, can read arbitrary files from the host running the JDBC client (application configuration, credential files, key stores, ...) through standard java.sql calls such as DatabaseMetaData.getImportedKeys(), getExportedKeys() or ResultSet.updateRow(). Exploitation requires control of the server side of the connection and allowLocalInfile enabled (the default). Setting allowLocalInfile=false is a workaround when LOAD DATA LOCAL INFILE is not needed. No integrity or availability impact.

    Credit

    Reported by buxuwa (buxu) through HackerOne

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

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

    Vendors and products

    Weakness classes (CWE)

    • CWE-20Improper Input Validation

      Class

      The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

      Entry at MITRE CWE-20

    • CWE-73External Control of File Name or Path

      Base

      The product allows user input to control or influence paths or file names that are used in filesystem operations.

      Entry at MITRE CWE-73

    References & sources

    • github.commariadb-corporation/mariadb-connector-j/commit/4d2f8002399949ed…x_refsource_MISC, web
    • github.commariadb-corporation/mariadb-connector-j/commit/5812e0ca7574c393…x_refsource_MISC, web
    • github.commariadb-corporation/mariadb-connector-j/commit/a4891f877f1c885a…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-119210advisory
    • 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. ReceivedGitHub

      CVSS V3.1: AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

      Weakness type: CWE-20, CWE-73

      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, 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.
      CVSSadded
      —
      AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
      Weakness type (CWE)added
      —
      CWE-20
      Weakness type (CWE)added
      —
      CWE-73
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/119xxx/CVE-2026-119210.json">CVE-2026-119210</a>
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/commit/4d2f8002399949ed7f138e9c0b75b69229538120
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/commit/5812e0ca7574c3934915179b76f2e819a556d099
      Referenceadded
      —
      https://github.com/mariadb-corporation/mariadb-connector-j/commit/a4891f877f1c885a573194771c1ed0aacec0ce1d
      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-fhx5-2xqw-2cgm

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