/

CVE-2026-55215

Severity:

HIGH RISK

(7.5)

TLS Certificate Validation (CWE-295) in MariaDB Node.js

CVE-2026-55215

Awaiting Analysis

Vulnerability type

Category:

Improper Certificate Validation

CWE:

CWE-295, CWE-522

Impact:

Database Credential Disclosure and Unauthorized Access

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

MariaDB Connector/Node.js may send database credentials before completing server certificate validation when TLS is enabled without a pinned CA or server certificate. An active man-in-the-middle could present a fraudulent certificate, capture the password through the clear-password authentication flow, and use it to authenticate directly even though the connector later rejects the connection.

Affected context

The issue occurs in MariaDB Connector/Node.js connections that enable SSL or TLS without pinning a trusted CA or server certificate. Risk is higher when the server selects mysql_clear_password initially or requests an authentication switch, because credential transmission may occur before the connector finishes its post-TLS server identity check.

Exploit preconditions

  • Attack surface: A network path between the Node.js application and the MariaDB or MySQL server
  • Required access: Ability to intercept and influence database connection traffic
  • Trigger point: TLS connection establishment followed by authentication negotiation
  • Configuration condition: SSL or TLS is enabled without a pinned CA or server certificate
  • Why exploitation is possible: Authentication credentials may be transmitted before certificate fingerprint validation completes

Why this happens

The vulnerability results from ordering and state-handling errors in the connector's TLS and authentication handshake. Credential transmission can occur before the peer identity has been fully validated, while authentication-switch processing may evaluate the previously selected plugin rather than the requested target plugin. This maps primarily to CWE-295: Improper Certificate Validation, with a related CWE-522: Insufficiently Protected Credentials, because an untrusted endpoint can receive database credentials before the connection is conclusively authenticated.

Potential impact

  • An attacker could capture database passwords
  • An attacker may authenticate directly to the database using stolen credentials
  • Database records could be read, modified, or deleted
  • Applications relying on the compromised database account could be affected
  • Exposed credentials could be reused against other systems

General mitigation guidance

Mitigation generally focuses on ensuring that server identity is established before any credential transmission.

Common defensive patterns include:

  • Pinning a trusted certificate authority or expected server certificate where operationally appropriate
  • Configuring TLS verification to fail closed when certificate validation cannot be completed
  • Avoiding clear-password authentication unless it is protected by a fully authenticated encrypted channel
  • Using authentication mechanisms that do not transmit reusable credentials prematurely
  • Restricting database-account privileges and separating application credentials by service
  • Protecting database traffic from interception through network segmentation and authenticated proxies
  • Maintaining connector dependencies through the organization's standard secure dependency-management process

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis of database connector configuration for disabled, incomplete, or non-pinned certificate verification
  • Code review of TLS-handshake and authentication-switch state transitions
  • Dependency and software-composition analysis for connector versions with known credential-ordering flaws
  • Network monitoring for database authentication attempts involving unexpected endpoints or certificate identities
  • Policy enforcement requiring verified server certificates and approved authentication plugins
  • Automated security review tools that flag credential transmission before peer authentication

Sources

SourceLink
github.comgithub.com/mariadb-corporation/mariadb-connector-nodejs/commit/514576a5a1fab3ea8498613e259a0b7a764e7302
github.comgithub.com/mariadb-corporation/mariadb-connector-nodejs/commit/c47d7275835c78c7eb8186cd23e9d57c045c128b
github.comgithub.com/mariadb-corporation/mariadb-connector-nodejs/commit/ecd36958e6e3bf0e0fa8389546f50c0ed6dbb2ac
github.comgithub.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.3.3
github.comgithub.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.4.6
github.comgithub.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.3
github.comgithub.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-cqhc-2h57-wpxf
hackerone.comhackerone.com/reports/3777370
jira.mariadb.orgjira.mariadb.org/browse/CONJS-349

Frequently asked

questions

Yes, when an attacker can actively intercept and influence traffic between the application and database server. It is primarily a network-position attack rather than a vulnerability that can generally be triggered through an ordinary application request.

The attacker needs a position that permits manipulation of the database connection handshake, such as control of an untrusted network, proxy, or intermediary. The attacker does not necessarily need prior database credentials.

Ensure the connector validates the database server's identity before sending credentials by using trusted or pinned certificate validation and authentication methods that do not expose reusable passwords prematurely.

Enforce TLS verification through configuration policy, review authentication state transitions, monitor database endpoints and certificates, apply least privilege to database accounts, and include dependency security checks in development and deployment workflows.

Find out what's already
exploitable in your codebase.