CVE-2026-55855: MariaDB has possible SQL injection in Buffer parameter escaping under big5/gbk/sjis/cp932/gb18030 client charsets
Summary A SQL injection is possible when the connector escapes Buffer parameters client-side under a multi-byte client character set whose trail-byte range overlaps the ASCII backslash (0x5C): big5, gbk, sjis, cp932, and gb18030.
Published Aug 28, 2026
Affected packages
mariadb
- Ecosystem
- npm
- Affected
- < 3.2.4
- Fixed in
- 3.2.4
- Check
npm ls mariadb
mariadb
- Ecosystem
- npm
- Affected
- >= 3.3.0, < 3.3.3
- Fixed in
- 3.3.4
- Check
npm ls mariadb
mariadb
- Ecosystem
- npm
- Affected
- >= 3.4.0, < 3.4.6
- Fixed in
- 3.4.6
- Check
npm ls mariadb
mariadb
- Ecosystem
- npm
- Affected
- >= 3.5.0, < 3.5.3
- Fixed in
- 3.5.3
- Check
npm ls mariadb
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A SQL injection is possible when the connector escapes Buffer parameters client-side under a multi-byte client character set whose trail-byte range overlaps the ASCII backslash (0x5C): big5, gbk, sjis, cp932, and gb18030. Under these charsets, an attacker-controlled lead byte can absorb the escape byte the connector inserts, leaving the following quote unescaped so it terminates the string literal and injected SQL is parsed.
Details
When binding a Buffer (binary) parameter, the connector escapes the value byte-by-byte, inserting a backslash (0x5C) before quote (0x27) and backslash bytes. This is correct under single-byte and UTF-8–family charsets, but unsafe under client charsets whose multi-byte trail-byte range includes 0x5C.
On the server, the SQL lexer performs multi-byte character recognition (my_ismbchar) before it interprets escape sequences. If character_set_client is one of the affected charsets and the attacker controls a byte the lexer treats as a valid lead byte, the sequence <0x5C> is consumed as a single multi-byte character. The escaping backslash inserted by the connector is swallowed as that character's trail byte, so the following 0x27 is no longer escaped — it closes the string literal, and the remaining bytes are parsed as SQL.
This is the well-known multi-byte escaping bypass (the same class that historically affected addslashes / mysql_real_escape_string under GBK/Big5), here applied to the connector's client-side Buffer escaping path.
Am I affected?
You are affected if all of the following hold:
You use mariadb Connector/Node.js at a version below the patched releases listed below. The connection's client character set is one of big5, gbk, sjis, cp932, or gb18030. This is not the default (the default is utf8mb4). Untrusted data can reach a Buffer-typed query parameter.
Applications using utf8mb4 (or any charset whose trail-byte range does not include 0x5C) are not affected by this vector. Parameters bound through the binary/server-side prepared-statement path are also not affected, because those values are sent out-of-band and are never escaped into the SQL text.
Impact
SQL injection. An attacker able to influence the contents of a Buffer parameter can break out of the intended string literal and inject arbitrary SQL, leading to unauthorized read or modification of data and, depending on the database account's privileges, further compromise.
Patches
Fixed in 3.2.4, 3.3.3, 3.4.6, and 3.5.3. Upgrade to the patched release on your branch:
- 3.5.x → 3.5.3
- 3.4.x → 3.4.6
- 3.3.x → 3.3.3
- 3.2.x and earlier → 3.2.4 (or any newer release)
Workarounds
If you cannot upgrade immediately:
Use server-side prepared statements (execute) so parameters are bound via the binary protocol rather than escaped into the SQL text. Avoid passing untrusted data as Buffer parameters under the affected charsets.
Credit
Reported by Yalguun Tumenkhuu (@fg0x0).
Credited to fg0x0.
References
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-g5xc-5w98-jfvm
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/0148cadba48064d430902678bbc5b4b62dc1c04f
- https://jira.mariadb.org/browse/CONJS-350
- https://github.com/advisories/GHSA-g5xc-5w98-jfvm
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-107382
MariaDB Connector/Node.js: Uncaught exception crashes the client during ed25519 authentication with zero-configuration TLS
medium5.9Oct 8, 2026CVE-2026-107383
MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters
high7.5Oct 8, 2026CVE-2026-107384
MariaDB Connector/Node.js: SQL injection through object keys in SET expansion (permitSetMultiParamEntries)
high8.1Oct 8, 2026CVE-2026-107385
MariaDB Connector/Node.js: SQL injection in the text protocol when the session uses NO_BACKSLASH_ESCAPES
high7.4Oct 8, 2026CVE-2026-55215
MariaDB's connector leaks the cleartext password to an MitM despite `ssl: true`
high7.5Aug 28, 2026CVE-2026-55854
MariaDB has Cleartext Transmission of Sensitive Information and Insufficiently Protected Credentials
medium5.9Aug 28, 2026
