CVE-2026-55215 json
MariaDB Connector/Node.js: Connector leaks the cleartext password to an MitM despite `ssl: true`
published 2026-08-28 2 mo ago modified 2026-09-08 2 mo ago also BIT-mariadb-2026-55215 , BIT-mariadb-min-2026-55215 , BIT-mysql-client-2026-55215 , EUVD-2026-67869 , GHSA-cqhc-2h57-wpxf
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm mariadb 3.2.4, 3.3.3, 3.4.6, 3.5.3
- bitnami mariadb 3.2.4
- bitnami mariadb-min 3.2.4
- bitnami mysql-client 3.2.4
- mariadb mariadb 3.2.4
- github.com/mariadb-corporation/mariadb-connector-nodejs@514576a commit
- github.com/mariadb-corporation/mariadb-connector-nodejs@c47d727 commit
- github.com/mariadb-corporation/mariadb-connector-nodejs@ecd3695 commit
- github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/… release
- github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/… release
- github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/… release
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | mariadb | <3.2.4 >=3.3.0, <3.3.3 >=3.4.0, <3.4.6 >=3.5.0, <3.5.3 |
3.2.4 3.3.3 3.4.6 3.5.3 |
| bitnami | mariadb | <3.2.4 |
3.2.4 |
| bitnami | mariadb-min | <3.2.4 |
3.2.4 |
| bitnami | mysql-client | <3.2.4 |
3.2.4 |
Affected products
- mariadb-corporation mariadb-connector-nodejs
Classification
- Weakness
- Technology feeds
References
-
github.com
/mariadb-corporation/mariadb-connector-nodejs/commit/514576a5a1fab3ea8498613e259a0b7a764e7302
web
-
github.com
/mariadb-corporation/mariadb-connector-nodejs/commit/c47d7275835c78c7eb8186cd23e9d57c045c128b
web
-
github.com
/mariadb-corporation/mariadb-connector-nodejs/commit/ecd36958e6e3bf0e0fa8389546f50c0ed6dbb2ac
web
-
github.com
/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-cqhc-2h57-wpxf
web
-
hackerone.com
/reports/3777370
web
-
github.com
/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.3.3
web
-
github.com
/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.4.6
web
-
github.com
/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.3
web
-
jira.mariadb.org
/browse/CONJS-349
web
-
github.com
/mariadb-corporation/mariadb-connector-nodejs
package
-
nvd.nist.gov
/vuln/detail/CVE-2026-55215
web
Sources
- CVE List CVE-2026-55215
- GitHub Advisory GHSA-cqhc-2h57-wpxf
- NVD CVE-2026-55215
- OSV BIT-mariadb-2026-55215
- OSV BIT-mariadb-min-2026-55215
- OSV BIT-mysql-client-2026-55215
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.