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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-119210)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-119210)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
478121	Chainguard: multiple keycloak-26.8 packages: security update to 26.8.1-r4	Tenable Cloud Security	Chainguard Local Security Checks	Local	medium
478121	Chainguard: multiple keycloak-26.8 packages: security update to 26.8.1-r4	Tenable Self-Hosted Container Security	Chainguard Local Security Checks	Local	medium
478099	SCA: security update for org.mariadb.jdbc:mariadb-java-client (GHSA-fhx5-2xqw-2cgm)	Tenable Cloud Security	SCA Checks	Local	medium
478099	SCA: security update for org.mariadb.jdbc:mariadb-java-client (GHSA-fhx5-2xqw-2cgm)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium
374241	Linux Distros Unpatched Vulnerability : CVE-2026-119210	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-119210

medium

Tenable Plugins

medium

medium

medium

medium

medium