SEPTEMBER 17, 2026
Live Feed
Back to database
Case File

CVE-2026-55857

MEDIUM · CVSS 5.9 EPSS 0.20% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-08-28 · Last synced 2026-09-17

CyberRota Analysis

AI-Generated

The MariaDB Connector/J versions prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9 are vulnerable to a flaw that allows PAM dialog authentication to transmit user passwords in cleartext over insecure connections, particularly when using default configurations with sslMode set to DISABLE. This vulnerability can be exploited by a man-in-the-middle attacker to intercept sensitive credentials during authentication. Organizations using affected versions of the MariaDB Connector/J, especially those with insecure network configurations, should prioritize upgrading to the patched versions to mitigate the risk of credential exposure.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-55857
Severity
MEDIUM
CVSS
5.9
EPSS
0.20%
Java

Original NVD Description

MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. Prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9, PAM dialog authentication can be coerced into transmitting the account password over an insecure connection. The mysql_clear_password plugin is gated behind a secure transport, but the sibling PAM handler SendPamAuthPacketFactory, named dialog by the server, does not declare that requirement and inherits the default secure-required value false; older branches implement the same affected behavior in SendPamAuthPacket. A hostile or man-in-the-middle server can send an Authentication Switch Request for dialog over plain TCP, causing the driver to return the user's password in cleartext when sslMode=DISABLE and restrictedAuth=null, which is the default configuration. Properly verified TLS and local Unix sockets are not exposed to this transport vector. This issue is fixed in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9.