CVE-2026-55855
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 23% of all known CVEs.
References
Related Vulnerabilities
Other CWE-89 (SQL Injection) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2014-3704 | High | 7.5 | 100% | - | Fix |
| CVE-2015-7297 | High | 7.5 | 100% | - | - |
| CVE-2024-29824 | High | 8.8 | 100% | KEV | Fix |
| CVE-2023-34362 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2019-7481 | High | 7.5 | 100% | KEV + Ransom | Fix |
| CVE-2024-29826 | High | 8.8 | 100% | - | Fix |
Common questions
How do I fix CVE-2026-55855?
No published fix for CVE-2026-55855 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-55855 being actively exploited?
Not that we know of. CVE-2026-55855 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.31% is the estimated probability that it will be exploited in the next 30 days. That is higher than 23% of all scored CVEs.
How severe is CVE-2026-55855?
CVE-2026-55855 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-55855
Markdown
[](https://tridentstack.com/cve/CVE-2026-55855)HTML
<a href="https://tridentstack.com/cve/CVE-2026-55855"><img src="https://tridentstack.com/cve/badge/CVE-2026-55855.svg" alt="CVE-2026-55855"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-28.