Vulnerability · CVE-2026-107382
MariaDB Connector/Node.js: Uncaught exception crashes the client during ed25519 authentication with zero-configuration TLS
Published Oct 8, 2026 · catalog updated Oct 16, 2026 · MariaDB Connector/Node.js: Uncaught exception
Check if you run it
No confirmed exploitation is on record for CVE-2026-107382. EPSS is 0.24%. Act only if a listed version of MariaDB Connector/Node.js: Uncaught exception is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (MariaDB Connector/Node.js: Uncaught exception).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium5.9
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.24%
- Remediation
- Advisory link
- Affected products
- Bitnami mariadb · Bitnami mariadb-min · Bitnami mysql-client · npm mariadb
### Description On the zero-configuration TLS path, the connector accepts a self-signed server certificate at the TLS level and then validates the server's identity from the fingerprint hash the server appends to the final OK_Packet ( ). That validation calls on the authentication plugin in use to obtain the password-derived secret both sides combine with the seed and the certificate fingerprint. referenced an identifier that was not in scope: it was neither a parameter of the method nor a module-scope binding, existing only as a parameter of the unrelated static . Invoking the method therefore threw . The throw happens synchronously inside the socket handler, and no frame between and the plugin guards it, so the error escapes as an uncaught exception rather than surfacing as a connection error. Because the fingerprint hash is what a legitimate MariaDB server sends on this path, ed25519 authentication with zero-configuration TLS never completed successfully — the failure is not limited to a hostile server. ### Impact Denial of service against the client process. Under Node's default behaviour the process exits, so a long-running service is terminated rather than seeing a failed connection attempt. No credential is disclosed and no data is altered; the impact is availability only. An unauthenticated attacker able to intercept the connection (a MitM presenting a self-signed certificate, or a compromised server) can trigger the crash at will, since the self-signed-certificate path is precisely what such an attacker exercises and the rogue server only has to answer the ed25519 challenge with an OK_Packet carrying a -prefixed validation hash. Exposure requires all of the following: a MariaDB server reached over TCP (not a unix socket), or an object without , a password set, no provided, and as the negotiated authentication plugin. Other authentication plugins are unaffected, as is any configuration where the server certificate is verified against a provided CA. ### Resol
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Bitnami mariadb3.3.0 → 3.5.4
- Bitnami mariadb-min3.3.0 → 3.5.4
- Bitnami mysql-client3.3.0 → 3.5.4
- npm mariadb3.3.0 → 3.5.4
How to fix CVE-2026-107382
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-107382. EPSS is 0.24%. Act only if a listed version of MariaDB Connector/Node.js: Uncaught exception is installed.
Which versions are affected?
Compare what you have installed with 3.3.0 → 3.5.4. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-248. EPSS 0.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 8, 2026 · GitHub Advisory Database
Detected
### Description On the zero-configuration TLS path, the connector accepts a self-signed server certificate at the TLS level and then validates the server's identity from the fingerprint hash the server appends to the final OK_Packet ( ). That validation calls on the authentication plugin in use to obtain the password-derived secret both sides combine with the seed and the certificate fingerprint.
Oct 16, 2026 · GitHub Advisory Database
Fix available
mariadb fixed in 3.5.4
Oct 16, 2026 · GitHub Advisory Database
Fix available
mariadb fixed in 3.5.4
Oct 16, 2026 · GitHub Advisory Database
Fix available
mariadb-min fixed in 3.5.4
Oct 16, 2026 · GitHub Advisory Database
Fix available
mariadb-min fixed in 3.5.4
Oct 16, 2026 · GitHub Advisory Database
Fix available
mysql-client fixed in 3.5.4
Oct 16, 2026 · GitHub Advisory Database
Fix available
mysql-client fixed in 3.5.4
Oct 16, 2026 · GitHub Advisory Database
Updated
### Description On the zero-configuration TLS path, the connector accepts a self-signed server certificate at the TLS level and then validates the server's identity from the fingerprint hash the server appends to the final OK_Packet ( ). That validation calls on the authentication plugin in use to obtain the password-derived secret both sides combine with the seed and the certificate fingerprint.
Sources
- CVE.orgVulnerability recordCVE-2026-107382
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-107382
30-day exploitation probability 0.2%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-cx2f-j9fh-8g68
GitHub Advisory Database record mirrored by OSV.
github.com - OpenSSF OSV / OSV ScannerPackage advisoryBIT-mariadb-2026-107382
MariaDB Connector/Node.js: Uncaught exception crashes the client during ed25519 authentication with zero-configuration TLS
osv.dev - OpenSSF OSV / OSV ScannerPackage advisoryBIT-mariadb-min-2026-107382
MariaDB Connector/Node.js: Uncaught exception crashes the client during ed25519 authentication with zero-configuration TLS
osv.dev - OpenSSF OSV / OSV ScannerPackage advisoryBIT-mysql-client-2026-107382
MariaDB Connector/Node.js: Uncaught exception crashes the client during ed25519 authentication with zero-configuration TLS
osv.dev - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-cx2f-j9fh-8g68
MariaDB Connector/Node.js: Uncaught exception crashes the client during ed25519 authentication with zero-configuration TLS
osv.dev
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.