Skip to content

MariaDB's connector leaks the cleartext password to an MitM despite `ssl: true`

High severity GitHub Reviewed Published Jul 9, 2026 in mariadb-corporation/mariadb-connector-nodejs • Updated Aug 28, 2026

Package

npm mariadb (npm)

Affected versions

< 3.2.4
>= 3.3.0, < 3.3.3
>= 3.4.0, < 3.4.6
>= 3.5.0, < 3.5.3

Patched versions

3.2.4
3.3.3
3.4.6
3.5.3

Description

Summary

When SSL/TLS is enabled but no CA / server certificate is provided, the
connector verifies the server's identity using fingerprint validation. The
check is effective, the connection is ultimately rejected when it fails,
but it happens after the authentication exchange. As a result, the
credentials are sent before validation occurs, so an active man-in-the-middle
who presents their own certificate receives the password in the handshake
before the connection is aborted.

Impact

The credentials are transmitted to the peer before the server's identity is
validated. An on-path attacker (MitM) presenting any certificate can capture
the account password, even though the connection then fails the fingerprint
check and is closed. The disclosed credentials can subsequently be used to
authenticate directly against the server.

  • Attacker requirement: active man-in-the-middle position on the network path
  • Affected configuration: SSL/TLS enabled without a CA / server certificate

Affected versions

  • < 3.2.4
  • 3.3.0 – 3.3.2
  • 3.4.0 – 3.4.5
  • 3.5.0 – 3.5.2

Patches

Fixed in 3.2.4, 3.3.3, 3.4.6, and 3.5.3. Upgrade to one of these (or later)
on your branch.

Workarounds

Until you can upgrade, configure certificate verification explicitly, provide
the server/CA certificate and use a verifying SSL mode (e.g. VERIFY_CA /
VERIFY_FULL).

Reported by haaahaaahiihiiii (no GitHub account).

References

@rusher rusher published to mariadb-corporation/mariadb-connector-nodejs Jul 9, 2026
Published to the GitHub Advisory Database Aug 28, 2026
Reviewed Aug 28, 2026
Last updated Aug 28, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(35th percentile)

Weaknesses

Improper Certificate Validation

The product does not validate, or incorrectly validates, a certificate. Learn more on MITRE.

Insufficiently Protected Credentials

The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. Learn more on MITRE.

CVE ID

CVE-2026-55215

GHSA ID

GHSA-cqhc-2h57-wpxf

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.