CVE-2026-107819
Received Received - Intake

MariaDB Connector/C TLS Hostname Verification Bypass

Publication date: 2026-10-09

Last updated on: 2026-10-09

Assigner: GitHub, Inc.

Description
MariaDB Connector/C is a C and C++ client library for connecting applications to MariaDB and MySQL databases. From 3.4.1 until 3.4.10, the MariaDB Connector/C libmariadb Zero-Configuration SSL authentication-switch logic checked certificate trust failure but did not reject a TLS hostname verification mismatch before selecting a non-hashing authentication plugin. An active man-in-the-middle attacker with a valid certificate for another hostname could request mysql_clear_password and obtain the database password inside the attacker-controlled TLS connection. Other MariaDB connectors are not affected. This issue is fixed in version 3.4.10.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-09
Last Modified
2026-10-09
Generated
2026-10-09
AI Q&A
2026-10-09
EPSS Evaluated
N/A
NVD
CVE-2026-107819
EUVD
EUVD-2026-95920

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
MariaDB server >= 3.4.1, < 3.4.10

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-297 The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

MariaDB Connector/C versions 3.4.1 to 3.4.10 have a flaw in SSL authentication-switch logic. When a certificate trust failure occurs, the connector does not reject TLS hostname verification mismatches before selecting a non-hashing authentication plugin. This allows an attacker with a valid certificate for another hostname to intercept and obtain the database password via mysql_clear_password.

Detection Guidance

Detecting this vulnerability requires checking the MariaDB Connector/C version in use. Run 'mysql_config --version' or check the library version in your application dependencies. If the version is between 3.4.1 and 3.4.9, the system is vulnerable.

Impact Analysis

An attacker could intercept database credentials during connection attempts. This could lead to unauthorized access to sensitive data stored in the database, potential data breaches, or further exploitation of the database system.

Compliance Impact

This vulnerability could lead to unauthorized access to personal or sensitive data, violating compliance requirements under GDPR and HIPAA. Organizations may face penalties, legal consequences, and reputational damage due to data breaches resulting from this issue.

Mitigation Strategies

Upgrade MariaDB Connector/C to version 3.4.10 or later immediately. Review and update authentication plugins to ensure TLS hostname verification is enforced. Monitor network traffic for unusual database password transmissions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-107819. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart