CVE-2026-55856: MariaDB Connector/J cleartext password disclosure in MITM

CVE-2026-55856 · Severity: medium · CVSS 5.9 · Published 2026-08-28

MariaDB Connector/J is a Java database driver used to connect applications to MariaDB databases. When configured with TLS verification (sslMode=verify-full/verify-ca) but without pinned certificates, an attacker positioned on the network can intercept the connection and steal the plaintext database password during the initial authentication handshake, before any certificate verification occurs. This allows the attacker to take over the database account and access all data the victim account can reach.

Technologies: org.mariadb.jdbc:mariadb-java-client (Maven). Vendors: Maven.

Quick answers

Is CVE-2026-55856 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-55856 being exploited in the wild.
How severe is CVE-2026-55856?
Medium severity, with a CVSS score of 5.9, published 28 August 2026.
Which products and versions are affected?
org.mariadb.jdbc:mariadb-java-client (Maven) ECOSYSTEM:introduced=0,fixed=2.7.14.
Is there a fix for CVE-2026-55856?
Yes. org.mariadb.jdbc:mariadb-java-client (Maven): upgrade to 2.7.14 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55856 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-55856?
Check whether you run org.mariadb.jdbc:mariadb-java-client (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.mariadb.jdbc:mariadb-java-client (Maven): upgrade to 2.7.14 or later
    # set org.mariadb.jdbc:mariadb-java-client to 2.7.14 in your pom.xml or build.gradle

Technical details

MariaDB Connector/J has an authentication bypass and credential disclosure vulnerability (CWE-522: Insufficiently Protected Credentials). When using sslMode=verify-full or verify-ca with a password but no pinned server certificate, the connector accepts a self-signed certificate at the TLS layer and defers identity verification via certificate fingerprint checking. However, the initial-handshake authentication path (HandshakeResponse.encode()) fails to enforce fingerprint verification before sending credentials with the mysql_clear_password plugin. An active network attacker can present a self-signed certificate, claim to be the MariaDB server, and receive the plaintext database password before any fingerprint validation occurs. The fingerprint check is correctly applied on the auth-switch and OK-packet paths but was missing from the initial-handshake path. The fix applies the same certFingerprint and MITM-proof checks to the initial-handshake path, refusing to send clear-password responses on unverified certificates. Patches are available in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9.

Affected products

  • MariaDB Connector/J < 2.7.14, >= 3.0.0 and < 3.3.5, >= 3.4.0 and < 3.4.3, >= 3.5.0 and < 3.5.9

Identifiers

  • CVE-2026-55856
  • GHSA-g9jj-cgmh-9f38

Timeline

  • 2026-07-09: disclosed: Vulnerability published to GitHub Advisory Database
  • 2026-06-09: patched: Fixes committed and released in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9
  • 2026-08-28: advisory: Advisory updated in GitHub Advisory Database

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.