MariaDB Connector/Node.js: Uncaught exception crashes the client during ed25519 authentication with zero-configuration TLS

Summary

MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. From 3.3.0 until 3.5.4, the zero-configuration TLS fingerprint-validation path calls Ed25519PasswordAuth.hash() through Authentication.validateFingerPrint, but Ed25519PasswordAuth.hash() references a seed identifier that is not in scope. Exposure requires a MariaDB server reached over TCP, TLS enabled with ssl: true or an ssl object whose rejectUnauthorized value is not false, a password set, no ssl.ca configured, and client_ed25519 negotiated as the authentication plugin. Under those conditions, a legitimate server, malicious server, or network attacker presenting a self-signed certificate can reach this path and cause a synchronous ReferenceError to escape the socket data handler. Under Node.js default uncaught-exception behavior, the client process terminates, causing denial of service. Configurations using a provided CA, rejectUnauthorized: false, another authentication plugin, or a Unix socket do not reach this vulnerable path. This issue is fixed in version 3.5.4.

Timeline

1. Oct 8, 2026, 6:24 PM UTCCVE published
2. Oct 8, 2026, 6:42 PM UTCCISA SSVC assessment

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

3. Oct 8, 2026, 6:42 PM UTCRecord last updated

Affected versions

• mariadb-corporation mariadb-connector-nodejs

  From 3.3.0 · fixed in 3.5.4

• mariadbBitnami

  From 3.3.0 · fixed in 3.5.4

• mariadb-minBitnami

  From 3.3.0 · fixed in 3.5.4

• mysql-clientBitnami

  From 3.3.0 · fixed in 3.5.4

• mariadbnpm

  From 3.3.0 · fixed in 3.5.4

References 5