<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 01 Nov 2026 11:51:32 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-119210</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-119210</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-119210</guid>
    </item>
    <item>
      <title>GHSA-fhx5-2xqw-2cgm — MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside quoted identifiers, letting a…</title>
      <link>https://db.gcve.eu/vuln/ghsa-fhx5-2xqw-2cgm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.mariadb.jdbc:mariadb-java-client&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;MariaDB Connector/J checked a server&amp;#39;s LOAD DATA LOCAL INFILE file request by
searching the text of the command it had sent for
`LOAD DATA LOCAL INFILE &amp;#39;&amp;lt;file&amp;gt;&amp;#39;`. 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.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;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 &amp;#34;does the
text appear anywhere in the SQL&amp;#34;, including inside a backtick-quoted identifier.&lt;/p&gt;
&lt;p&gt;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 &amp;#39;/etc/passwd&amp;#39;`` makes the connector send
``SHOW CREATE TABLE `LOAD DATA LOCAL INFILE &amp;#39;/etc/passwd&amp;#39;`.`accounts` ``;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.mariadb.jdbc:mariadb-java-client&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;MariaDB Connector/J checked a server&amp;#39;s LOAD DATA LOCAL INFILE file request by
searching the text of the command it had sent for
`LOAD DATA LOCAL INFILE &amp;#39;&amp;lt;file&amp;gt;&amp;#39;`. 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.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;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 &amp;#34;does the
text appear anywhere in the SQL&amp;#34;, including inside a backtick-quoted identifier.&lt;/p&gt;
&lt;p&gt;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 &amp;#39;/etc/passwd&amp;#39;`` makes the connector send
``SHOW CREATE TABLE `LOAD DATA LOCAL INFILE &amp;#39;/etc/passwd&amp;#39;`.`accounts` ``;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-fhx5-2xqw-2cgm</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-119210</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-119210</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:18.04:LTS: mariadb-connector-java, Ubuntu:20.04:LTS: mariadb-connector-java, Ubuntu:22.04:LTS: mariadb-connector-java, Ubuntu:24.04:LTS: mariadb-connector-java, Ubuntu:26.10: mariadb-connector-java, Ubuntu:26.04:LTS: mariadb-connector-java&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:18.04:LTS: mariadb-connector-java, Ubuntu:20.04:LTS: mariadb-connector-java, Ubuntu:22.04:LTS: mariadb-connector-java, Ubuntu:24.04:LTS: mariadb-connector-java, Ubuntu:26.10: mariadb-connector-java, Ubuntu:26.04:LTS: mariadb-connector-java&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-119210</guid>
    </item>
  </channel>
</rss>
