CVE-2026-55215: CWE-295: Improper Certificate Validation in mariadb-corporation mariadb-connector-nodejs
Description
MariaDB Connector/Node.js versions prior to 3.3.3, 3.4.6, and 3.5.3 have an improper certificate validation vulnerability. When SSL is enabled without a pinned CA or server certificate, the connector may send credentials before completing certificate fingerprint validation. This allows a man-in-the-middle attacker to present a self-signed certificate, capture the database password, and authenticate directly even though the connection is later closed. The issue is fixed in versions 3.3.3, 3.4.6, and 3.5.3.
CVSS v3.1
Score 7.5high
Affected software
mariadb-corporation
mariadb-connector-nodejs
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
MariaDB Connector/Node.js versions before 3.3.3, 3.4.6, and 3.5.3 improperly validate server certificates when SSL is enabled without pinned CA or server certificates. Specifically, the connector sends credentials before completing certificate fingerprint validation during the handshake process. An attacker performing a man-in-the-middle attack can present a self-signed certificate, capture the password sent via the mysql_clear_password authentication plugin, and use it to authenticate directly, even though the connector eventually rejects the server and closes the connection. This vulnerability is tracked as CVE-2026-55215 and relates to CWE-295 (Improper Certificate Validation) and CWE-522 (Insufficiently Protected Credentials).
Potential Impact
An attacker capable of man-in-the-middle interception can capture database credentials by exploiting the premature sending of credentials before certificate validation completes. This compromises the confidentiality of the database password, potentially allowing unauthorized access to the database. The vulnerability does not affect integrity or availability directly but exposes sensitive credentials.
Mitigation Recommendations
Upgrade MariaDB Connector/Node.js to version 3.3.3, 3.4.6, or 3.5.3 or later, where this issue is fixed. Until upgraded, avoid enabling SSL without pinned CA or server certificates to prevent exposure of credentials before certificate validation completes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T16:16:32.627Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a91e40cacd9273b4942e825
Added to database: 08/28/2026, 19:39:56 UTC
Last enriched: 09/07/2026, 15:14:18 UTC
Last updated: 10/11/2026, 06:48:17 UTC
Views: 34
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.