CVE-2026-55215
HIGHDescription
MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. Prior to versions 3.3.3, 3.4.6, and 3.5.3, when ssl is enabled without a pinned CA or server certificate, MariaDB Connector/Node.js sends credentials before completing certificate fingerprint validation. In lib/cmd/handshake/auth/handshake.js, a server that selects mysql_clear_password as the initial authentication plugin can receive the password before the post-TLS identity check. In lib/cmd/handshake/authentication.js, an authentication switch can evaluate the previous plugin instead of the requested target plugin, allowing mysql_clear_password to send the credential first. An active man-in-the-middle can present a self-signed certificate, capture the database password, and use it to authenticate directly even though the connector later rejects the server and closes the connection. This issue is fixed in versions 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:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 35% of all known CVEs.
References
Related Vulnerabilities
Other CWE-295 (Improper Certificate Validation) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2015-4000 | Low | 3.7 | 100% | - | Fix |
| CVE-2020-0601 | High | 8.1 | 89% | KEV | Fix |
| CVE-2009-3555 | Critical | 9.8 | 87% | - | Fix |
| CVE-2022-26923 | High | 8.8 | 84% | KEV | Fix |
| CVE-2023-27823 | Critical | 9.8 | 53% | - | - |
| CVE-2022-42979 | High | 8.8 | 24% | - | - |
Common questions
How do I fix CVE-2026-55215?
No published fix for CVE-2026-55215 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-55215 being actively exploited?
Not that we know of. CVE-2026-55215 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.42% is the estimated probability that it will be exploited in the next 30 days. That is higher than 35% of all scored CVEs.
How severe is CVE-2026-55215?
CVE-2026-55215 has a CVSS v3 base score of 7.5, rated high. 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-55215
Markdown
[](https://tridentstack.com/cve/CVE-2026-55215)HTML
<a href="https://tridentstack.com/cve/CVE-2026-55215"><img src="https://tridentstack.com/cve/badge/CVE-2026-55215.svg" alt="CVE-2026-55215"></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.