MariaDB Connector/Node.js: Possible SQL injection in Buffer parameter escaping under big5/gbk/sjis/cp932/gb18030 client charsets
Summary
| CVE | CVE-2026-55855 |
|---|---|
| State | PUBLISHED |
| Assigner | GitHub_M |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-28 23:17:08 UTC |
| Updated | 2026-08-28 23:17:08 UTC |
| Description | MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. Prior to 3.2.4, 3.3.3, 3.4.6, and 3.5.3, MariaDB Connector/Node.js permits SQL injection when attacker-controlled Buffer parameters are escaped client-side under the big5, gbk, sjis, cp932, or gb18030 client character sets. PacketOutputStream.writeBufferEscape in lib/io/packet-output-stream.js escaped bytes without the charset-aware getMbRecognizer logic in lib/misc/charset-mb.js. The server SQL lexer runs my_ismbchar before escape processing, so an attacker-controlled lead byte can consume the inserted 0x5C backslash as a multibyte trail byte and leave the following 0x27 quote unescaped, terminating the string literal and allowing arbitrary SQL. The default utf8mb4 character set and parameters sent through the execute binary prepared-statement path are not affected. Successful exploitation can expose or modify data available to the database account. This issue is fixed in versions 3.2.4, 3.3.3, 3.4.6, and 3.5.3. |
Risk And Classification
Primary CVSS: v3.1 6.5 MEDIUM from [email protected]
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
Problem Types: CWE-89 | CWE-116 | CWE-89 CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') | CWE-116 CWE-116: Improper Encoding or Escaping of Output
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 6.5 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N |
| 3.1 | CNA | DECLARED | 6.5 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
HighPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
LowAvailability
NoneCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Mariadb-corporation | Mariadb-connector-nodejs | affected < 3.2.4 | Not specified |
| CNA | Mariadb-corporation | Mariadb-connector-nodejs | affected >= 3.3.0, < 3.3.3 | Not specified |
| CNA | Mariadb-corporation | Mariadb-connector-nodejs | affected >= 3.4.0, < 3.4.6 | Not specified |
| CNA | Mariadb-corporation | Mariadb-connector-nodejs | affected >= 3.5.0, < 3.5.3 | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.2.4 | [email protected] | github.com | |
| github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.3.3 | [email protected] | github.com | |
| github.com/mariadb-corporation/mariadb-connector-nodejs/commit/97f183f33... | [email protected] | github.com | |
| jira.mariadb.org/browse/CONJS-350 | [email protected] | jira.mariadb.org | |
| github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.4.6 | [email protected] | github.com | |
| github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.3 | [email protected] | github.com | |
| github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisor... | [email protected] | github.com | |
| github.com/mariadb-corporation/mariadb-connector-nodejs/commit/26e35f9ed... | [email protected] | github.com | |
| github.com/mariadb-corporation/mariadb-connector-nodejs/commit/7af8b7b8b... | [email protected] | github.com | |
| github.com/mariadb-corporation/mariadb-connector-nodejs/commit/25c6239b6... | [email protected] | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.