Read the docs

SQL injection in MariaDB Connector/Node.js with NO_BACKSLASH_ESCAPES

Priority LOW 35CWE-89Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
SQL injection
Confidentiality · integrity · availability
None · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-89.

Summary

MariaDB Connector/Node.js before 3.2.5, from 3.3.0 before 3.3.4, from 3.4.0 before 3.4.7, and from 3.5.0-rc.0 before 3.5.4 does not escape quotes correctly when the session uses NO_BACKSLASH_ESCAPES (CWE-89). Text-protocol escaping adds a backslash that is an ordinary character in that mode, so a placeholder value can end the SQL string literal. A remote attacker can inject arbitrary SQL with the application's database privileges.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

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'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'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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00438 38th percentileScored 2026-11-07
Fix Fixed mariadb-connector-nodejs (mariadb-corporation): 3.2.5, 3.3.4, 3.4.7 +1mariadb (npm): 3.2.5, 3.3.4, 3.4.7 +1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
MariaDBmariadb-connector-nodejsbefore 3.2.5; 3.3.0 to before 3.3.4; 3.4.0 to before 3.4.7; 3.5.0-rc.0 to before 3.5.43.2.5, 3.3.4, 3.4.7, 3.5.4Patch availableCNA
—mariadb (npm)before 3.2.53.2.5Patch availableGHSA-r3rv-jm3r-62q2
—mariadb (npm)3.3.0 to before 3.3.43.3.4Patch availableGHSA-r3rv-jm3r-62q2
—mariadb (npm)3.4.0 to before 3.4.73.4.7Patch availableGHSA-r3rv-jm3r-62q2
—mariadb (npm)3.5.0-rc.0 to before 3.5.43.5.4Patch availableGHSA-r3rv-jm3r-62q2
  • mariadb-connector-nodejs VendorMariaDB Affected before 3.2.5; 3.3.0 to before 3.3.4; 3.4.0 to before 3.4.7; 3.5.0-rc.0 to before 3.5.4 Fixed in 3.2.5, 3.3.4, 3.4.7, 3.5.4 Patch available CNA
  • mariadb (npm) Vendor— Affected before 3.2.5 Fixed in 3.2.5 Patch available GHSA-r3rv-jm3r-62q2
  • mariadb (npm) Vendor— Affected 3.3.0 to before 3.3.4 Fixed in 3.3.4 Patch available GHSA-r3rv-jm3r-62q2
  • mariadb (npm) Vendor— Affected 3.4.0 to before 3.4.7 Fixed in 3.4.7 Patch available GHSA-r3rv-jm3r-62q2
  • mariadb (npm) Vendor— Affected 3.5.0-rc.0 to before 3.5.4 Fixed in 3.5.4 Patch available GHSA-r3rv-jm3r-62q2

Remediation

Upgrade mariadb-connector-nodejs to 3.2.5, 3.3.4, 3.4.7, or 3.5.4, matching the release line in use, and upgrade the npm package mariadb to the same fixed version.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

  • Fix · CNA mariadb-connector-nodejs (mariadb-corporation) Fixed in 3.2.5, 3.3.4, 3.4.7, 3.5.4
  • Fix · GHSA-r3rv-jm3r-62q2 mariadb (npm) Fixed in 3.2.5 Advisory →
  • Fix · GHSA-r3rv-jm3r-62q2 mariadb (npm) Fixed in 3.3.4 Advisory →
  • Fix · GHSA-r3rv-jm3r-62q2 mariadb (npm) Fixed in 3.4.7 Advisory →
  • Fix · GHSA-r3rv-jm3r-62q2 mariadb (npm) Fixed in 3.5.4 Advisory →

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-09 Threatist record created from CVE-2026-107385
  2. 2026-10-09 Alias added: GHSA-r3rv-jm3r-62q2
  3. 2026-10-09 CISA SSVC decision points changed
  4. 2026-10-09 Priority changed: MEDIUM → LOW
  5. 2026-11-06 Affected versions changed · Red Hat
  6. 2026-11-06 CVSS score added · Red Hat

References

  • TI-2023-11776 MariaDB v10.5 was discovered to contain a remote code execution (RCE) vulnerability via… CVSS 3.1CRITICAL 9.8
  • TI-2016-05707 Oracle MySQL through 5.5.52, 5.6.x through 5.6.33, and 5.7.x through 5.7.15; MariaDB… CVSS 3.0CRITICAL 9.8
  • TI-2022-00687 Infinite loop in BN_mod_sqrt() reachable when parsing certificates CVSS 3.1HIGH 7.5
  • TI-2014-00217 OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly… CVSS 3.1HIGH 7.4
  • TI-2014-00188 The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0… CVSS 2.0MEDIUM 6.8
  • TI-2018-15259 zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if… CVSS 3.1HIGH 7.5
See all 459 →

Sources