SQL Injection Affecting sqlpad package, versions <7.5.7-r39
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-SQLPAD-19641786
- published8 Sept 2026
- disclosed28 Aug 2026
Introduced: 28 Aug 2026
CVE-2026-55855 (opens in a new tab)How to fix?
Upgrade Chainguard sqlpad to version 7.5.7-r39 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream sqlpad package and not the sqlpad package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
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.
References
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/25c6239b68fd909132355c3f8535a5ef32423468
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/26e35f9edb00bcf249627a564e0052fba7b305a2
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/7af8b7b8b7ae5e1a081693ade989f5a80c8e06e3
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/97f183f33b5d4e6767b34ecabdd81fe3294a80a6
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.2.4
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.3.3
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.4.6
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.3
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-g5xc-5w98-jfvm
- https://jira.mariadb.org/browse/CONJS-350