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

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-55856— MariaDB Connector/J: Cleartext password disclosure to a MITM on the initial-handshake

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 之前的版本中，当 Java 应用程序以 或 进行连接、提供了密码，且未配置 或 时，Connector/J 可能会通过 的临时信任管理器接受一个不受信任的自签名证书，并记录其证书指纹（certFingerprint）以便后续进行身份绑定。虽然 OK 数据包路径和认证切换路径会强制校验证书指纹，但初始握手（initial-handshak

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

I. Basic Information for CVE-2026-55856

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 password disclosure to a MITM on the initial-handshake
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, when a Java application connects with sslMode=verify-full or sslMode=verify-ca, supplies a password, and does not configure serverSslCert or trustStore, Connector/J can accept an untrusted self-signed certificate through the fallbackToSystemTrustStore=true ephemeral trust manager and record its certFingerprint for later identity binding. The OK-packet and authentication-switch paths enforce the certificate fingerprint, but the initial-handshake path does not. HandshakeResponse.encode() can therefore build and send a mysql_clear_password response before checking certFingerprint != null && !isMitMProof(), sslMode, or whether the authentication plugin is resistant to a man-in-the-middle, and the initial path also bypasses restrictedAuth. An active man-in-the-middle or hostile server can present a self-signed certificate, claim to be MariaDB, select mysql_clear_password as the initial authentication plugin, and receive the full database password before the connection is rejected. 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-55856

# 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-55856

请登录查看更多情报信息。

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

Vendor Advisories for CVE-2026-55856 (1)

Vendor Pages for CVE-2026-55856 (3)

Other References for CVE-2026-55856 (1)

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-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-55857 5.9 MEDIUM MariaDB Connector/J: Cleartext Transmission of Sensitive Information and Insufficiently Pr
CVE-2026-55858 5.9 MEDIUM MariaDB Connector/J: Inappropriate Encoding for Output Context in org.mariadb.jdbc:mariadb

IV. Related Vulnerabilities

Same product: mariadb-connector-j
Same vendor: mariadb-corporation
Same weakness: CWE-522

V. Comments for CVE-2026-55856

No comments yet

Leave a comment