Skip to content
Fencer Vulns
medium 6.5

CVE-2026-55855 json

MariaDB Connector/Node.js: Possible SQL injection in Buffer parameter escaping under big5/gbk/sjis/cp932/gb18030 client charsets

published 2026-08-28 2 mo ago modified 2026-09-08 2 mo ago also BIT-mariadb-2026-55855 , BIT-mariadb-min-2026-55855 , BIT-mysql-client-2026-55855 , EUVD-2026-68011 , GHSA-g5xc-5w98-jfvm

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm mariadb 3.2.4, 3.3.4, 3.4.6, 3.5.3
  • bitnami mariadb 3.2.4, 3.3.3, 3.4.6, 3.5.3
  • bitnami mariadb-min 3.2.4, 3.3.3, 3.4.6, 3.5.3
  • bitnami mysql-client 3.2.4, 3.3.3, 3.4.6, 3.5.3
  • mariadb mariadb 3.2.4, 3.3.3, 3.4.6, 3.5.3

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm mariadb
<3.2.4
>=3.3.0, <3.3.4
>=3.4.0, <3.4.6
>=3.5.0, <3.5.3
3.2.4
3.3.4
3.4.6
3.5.3
bitnami mariadb
<3.2.4
>=3.3.0, <3.3.3
>=3.4.0, <3.4.6
>=3.5.0, <3.5.3
3.2.4
3.3.3
3.4.6
3.5.3
bitnami mariadb-min
<3.2.4
>=3.3.0, <3.3.3
>=3.4.0, <3.4.6
>=3.5.0, <3.5.3
3.2.4
3.3.3
3.4.6
3.5.3
bitnami mysql-client
<3.2.4
>=3.3.0, <3.3.3
>=3.4.0, <3.4.6
>=3.5.0, <3.5.3
3.2.4
3.3.3
3.4.6
3.5.3

Affected products

  • mariadb-corporation mariadb-connector-nodejs

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command
  • CWE-116 Improper Encoding or Escaping of Output
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.