Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-55857— MariaDB Connector/J: Cleartext Transmission of Sensitive Information and Insufficiently Protected Credentials

Quick assessment

Affected
mariadb-corporation mariadb-connector-j
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

MariaDB Connector/J 用于将使用 Java 开发的应用程序连接到 MariaDB 和 MySQL 数据库。在 2.7.14、3.3.5、3.4.3 和 3.5.9 之前版本中,PAM 对话框认证可能被强制在不安全的连接上传输账户密码。 插件要求通过安全传输(secure transport)进行门控,但其姊妹 PAM 处理器 (在服务器端被称为 dialog)并未声明这一要求,并继承了默认的“无需安全传输”(secure-required = false)设置;更早的分支中, 也实现了相同的行为。

CVSS 5.9 · Medium
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-55857

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
MariaDB Connector/J: Cleartext Transmission of Sensitive Information and Insufficiently Protected Credentials
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
敏感数据的明文传输
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
mariadb-corporation mariadb-connector-j < 2.7.14 -

II. Public POCs for CVE-2026-55857

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-55857

登录查看更多情报信息。

Patches & Fixes for CVE-2026-55857 (2)

Vendor Advisories for CVE-2026-55857 (1)

Vendor Pages for CVE-2026-55857 (3)

Same Patch Batch · mariadb-corporation · 2026-08-28 · 8 CVEs total

CVE-2026-55215 7.5 HIGH MariaDB Connector/Node.js: Connector leaks the cleartext password to an MitM despite `ssl:
CVE-2026-55855 6.5 MEDIUM MariaDB Connector/Node.js: Possible SQL injection in Buffer parameter escaping under big5/
CVE-2026-55854 5.9 MEDIUM MariaDB Connector/Node.js: Cleartext Transmission of Sensitive Information and Insufficien
CVE-2026-55856 5.9 MEDIUM MariaDB Connector/J: Cleartext password disclosure to a MITM on the initial-handshake
CVE-2026-55860 5.9 MEDIUM MariaDB Connector/R2DBC: Cleartext password disclosure to a man-in-the-middle server (clea
CVE-2026-55859 5.9 MEDIUM MariaDB Connector/R2DBC: Inappropriate Encoding for Output Context and Improper Encoding o
CVE-2026-55858 5.9 MEDIUM MariaDB Connector/J: Inappropriate Encoding for Output Context in org.mariadb.jdbc:mariadb

IV. Related Vulnerabilities

V. Comments for CVE-2026-55857

No comments yet


Leave a comment