Skip to main content
← All vulnerabilities
CVE-2026-55854GHSA-42R5-VHPQ-M858BIT-MARIADB-2026-55854BIT-MARIADB-MIN-2026-55854BIT-MYSQL-CLIENT-2026-55854

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

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 3.2.4, 3.3.3, 3.4.6, 3.5.3
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • mariadb-corporation mariadb-connector-nodejs

    fixed in 3.2.4; From 3.3.0 · fixed in 3.3.3; From 3.4.0 · fixed in 3.4.6; From 3.5.0 · fixed in 3.5.3

  • mariadbnpm

    fixed in 3.2.4

  • mariadbnpm

    From 3.3.0 · fixed in 3.3.3

  • mariadbnpm

    From 3.4.0 · fixed in 3.4.6

  • mariadbnpm

    From 3.5.0 · fixed in 3.5.3

References 10

GitHub · mariadb-corporation/mariadb-connector-nodejs

jira.mariadb.org