CVE-2026-55856: CWE-522: Insufficiently Protected Credentials in mariadb-corporation mariadb-connector-j
Description
MariaDB Connector/J versions prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9 contain a vulnerability where the initial handshake path does not properly enforce certificate fingerprint verification. This allows a man-in-the-middle or hostile server to present a self-signed certificate and receive the full database password via the mysql_clear_password authentication plugin before the connection is rejected.
CVSS v3.1
Score 5.9medium
Affected software
mariadb-corporation
mariadb-connector-j
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
MariaDB Connector/J, used for Java applications connecting to MariaDB and MySQL databases, has an insufficiently protected credential vulnerability (CWE-522) in versions before 2.7.14, 3.3.5, 3.4.3, and 3.5.9. When connecting with sslMode=verify-full or sslMode=verify-ca, if serverSslCert or trustStore are not configured, the connector accepts an untrusted self-signed certificate via fallbackToSystemTrustStore=true and records its certFingerprint. While the OK-packet and authentication-switch paths enforce this fingerprint, the initial-handshake path does not. This flaw allows an attacker performing a man-in-the-middle attack or a hostile server to present a self-signed certificate, select mysql_clear_password as the initial authentication plugin, and receive the full database password before the connection is rejected.
Potential Impact
An attacker capable of man-in-the-middle or controlling the server can obtain the full database password sent in clear text during the initial handshake, potentially compromising database credentials. The vulnerability does not impact integrity or availability but results in high confidentiality impact due to credential exposure.
Mitigation Recommendations
This vulnerability is fixed in MariaDB Connector/J versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9. Users should upgrade to these or later versions to remediate the issue. No other mitigations are indicated in the vendor advisory. Patch status is not explicitly stated beyond the fixed versions; users should verify with official vendor advisories for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-17T16:44:40.995Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a92113dacd9273b496f46ad
Added to database: 08/28/2026, 22:52:45 UTC
Last enriched: 09/07/2026, 15:27:14 UTC
Last updated: 10/12/2026, 06:48:17 UTC
Views: 110
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.