<?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://vulnerability.circl.lu</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, 11 Oct 2026 16:25:06 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-107385</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-107385</link>
      <description>&lt;p&gt;MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. Prior to 3.2.5, 3.3.4, 3.4.7, and 3.5.4, text-protocol escaping always prefixes quotes with a backslash and does not honor the session&amp;#39;s NO_BACKSLASH_ESCAPES mode, including in Connection.escape(). When that mode is enabled, the backslash is an ordinary character, so an attacker-controlled placeholder value can close the SQL string literal and inject arbitrary SQL with the application&amp;#39;s database privileges. The vulnerable configuration may be enabled server-wide, through connector initialization options, or with an application-issued SET sql_mode; execute() and batch() use binary protocols and are not affected. This issue is fixed in versions 3.2.5, 3.3.4, 3.4.7, and 3.5.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. Prior to 3.2.5, 3.3.4, 3.4.7, and 3.5.4, text-protocol escaping always prefixes quotes with a backslash and does not honor the session&amp;#39;s NO_BACKSLASH_ESCAPES mode, including in Connection.escape(). When that mode is enabled, the backslash is an ordinary character, so an attacker-controlled placeholder value can close the SQL string literal and inject arbitrary SQL with the application&amp;#39;s database privileges. The vulnerable configuration may be enabled server-wide, through connector initialization options, or with an application-issued SET sql_mode; execute() and batch() use binary protocols and are not affected. This issue is fixed in versions 3.2.5, 3.3.4, 3.4.7, and 3.5.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-107385</guid>
    </item>
    <item>
      <title>GHSA-r3rv-jm3r-62q2 — MariaDB Connector/Node.js: SQL injection in the text protocol when the session uses NO_BACKSLASH_ESCAPES</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-r3rv-jm3r-62q2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: mariadb&lt;/p&gt;
&lt;p&gt;### Description
When escaping string and binary parameters for the text protocol, the connector always escaped the quote character with a backslash, without ever consulting the session&amp;#39;s NO_BACKSLASH_ESCAPES SQL mode. The server status flag was declared (STATUS_NO_BACKSLASH_ESCAPES) but never read.&lt;/p&gt;
&lt;p&gt;Under a server or session running with NO_BACKSLASH_ESCAPES, the backslash is an ordinary character and the quote must be escaped by doubling it. The escaped value produced by the connector therefore closed the string literal, and a value passed through a placeholder was interpreted as SQL.&lt;/p&gt;
&lt;p&gt;All text-protocol escaping entry points were affected, including Connection.escape().&lt;/p&gt;
&lt;p&gt;### Impact
An attacker able to influence any value the application passes as a query parameter could execute arbitrary SQL with the privileges of the application&amp;#39;s database user: read, modify or delete any data reachable by that connection.&lt;/p&gt;
&lt;p&gt;Exposure requires a deployment where NO_BACKSLASH_ESCAPES is enabled — server-wide, through the connector&amp;#39;s sessionVariables / initSql options, or by an application-issued SET sql_mode. It is not implied by the ANSI, ORACLE or TRADITIONAL compound modes on MariaDB 11.4, so it has to be set deliberately. Where it is enabled, no unusual application code is needed: the standard placeholder API is the injection point.&lt;/p&gt;
&lt;p&gt;execute() and batch() are not affected: the binary prepared-statement and bulk protocols send parameter values out of band.&lt;/p&gt;
&lt;p&gt;### Resolution
The escaping rout…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: mariadb&lt;/p&gt;
&lt;p&gt;### Description
When escaping string and binary parameters for the text protocol, the connector always escaped the quote character with a backslash, without ever consulting the session&amp;#39;s NO_BACKSLASH_ESCAPES SQL mode. The server status flag was declared (STATUS_NO_BACKSLASH_ESCAPES) but never read.&lt;/p&gt;
&lt;p&gt;Under a server or session running with NO_BACKSLASH_ESCAPES, the backslash is an ordinary character and the quote must be escaped by doubling it. The escaped value produced by the connector therefore closed the string literal, and a value passed through a placeholder was interpreted as SQL.&lt;/p&gt;
&lt;p&gt;All text-protocol escaping entry points were affected, including Connection.escape().&lt;/p&gt;
&lt;p&gt;### Impact
An attacker able to influence any value the application passes as a query parameter could execute arbitrary SQL with the privileges of the application&amp;#39;s database user: read, modify or delete any data reachable by that connection.&lt;/p&gt;
&lt;p&gt;Exposure requires a deployment where NO_BACKSLASH_ESCAPES is enabled — server-wide, through the connector&amp;#39;s sessionVariables / initSql options, or by an application-issued SET sql_mode. It is not implied by the ANSI, ORACLE or TRADITIONAL compound modes on MariaDB 11.4, so it has to be set deliberately. Where it is enabled, no unusual application code is needed: the standard placeholder API is the injection point.&lt;/p&gt;
&lt;p&gt;execute() and batch() are not affected: the binary prepared-statement and bulk protocols send parameter values out of band.&lt;/p&gt;
&lt;p&gt;### Resolution
The escaping rout…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-r3rv-jm3r-62q2</guid>
    </item>
  </channel>
</rss>
