Skip to content
Fencer Vulns
medium 5.9

CVE-2026-55854 json

MariaDB Connector/Node.js: Cleartext Transmission of Sensitive Information and Insufficiently Protected Credentials in mariadb

published 2026-08-28 2 mo ago modified 2026-09-08 2 mo ago also BIT-mariadb-2026-55854 , BIT-mariadb-min-2026-55854 , BIT-mysql-client-2026-55854 , EUVD-2026-68010 , GHSA-42r5-vhpq-m858

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
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 3.2.4, 3.3.3, 3.4.6, and 3.5.3, MariaDB Connector/Node.js can disclose an account password when PAM dialog authentication is negotiated over an insecure transport. In lib/cmd/handshake/auth/pam-password-auth.js and lib/cmd/handshake/authentication.js, the SendPamAuthPacketFactory behavior for the server-side plugin dialog lacked the secure-transport gate applied to mysql_clear_password. With the default sslMode=DISABLE and restrictedAuth=null settings, a hostile or on-path server can send an Authentication Switch Request for dialog over plain TCP, causing the connector to return the account password in cleartext. Properly verified TLS and a local Unix socket prevent this path, while fingerprint-only server identity validation is not sufficient. This issue is fixed in versions 3.2.4, 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, 3.3.3, 3.4.6, 3.5.3
  • bitnami mariadb-min 3.2.4, 3.3.3, 3.4.6, 3.5.3
  • bitnami mysql-client 3.2.4, 3.3.3, 3.4.6, 3.5.3
  • mariadb mariadb 3.2.4, 3.3.3, 3.4.6, 3.5.3

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 5.9 CVSS:3.1/AV:N/AC:H/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.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-min
<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 mysql-client
<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

Affected products

  • mariadb-corporation mariadb-connector-nodejs

Classification

Weakness
  • CWE-319 Cleartext Transmission of Sensitive Information
  • CWE-522 Insufficiently Protected Credentials
Technology feeds

References

Sources

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.