Vulnerability in org.mariadb.jdbc:mariadb-java-client (CVE-2026-55856)
Summary
Vulnerability in org.mariadb.jdbc:mariadb-java-client (CVE-2026-55856). Confidential information can be exposed externally. Mitigation: upgrade to 2.7.14 or later.
Original description
The description as published by the source.
Summary
When a Java application connects with sslMode=verify-full (or verify-ca) and a password but does not pin a server certificate, Connector/J deliberately accepts an untrusted/self-signed certificate at the TLS layer (the "MITM-proof without a CA" feature) and proves the server's identity afterwards by binding the certificate fingerprint into the authentication exchange. That fingerprint enforcement is applied to the OK-packet and auth-switch paths but not to the initial-handshake path. An active man-in-the-middle that presents a self-signed certificate, claims to be MariaDB, and names the initial authentication plugin mysql_clear_password receives the victim's database password in cleartext, before any fingerprint/identity check runs. The connection is torn down a moment later, but the credential is already gone.
Details
For sslMode=verify-full/verify-ca with a password and no serverSslCert/trustStore, the connector falls back to an ephemeral trust manager (default fallbackToSystemTrustStore=true) that accepts any non-expired certificate at the TLS layer and records its fingerprint. Identity is then meant to be enforced via that fingerprint.
The enforcement guard is present on two of the three paths, the OK-packet fingerprint check and the auth-switch handler (where the clear-password plugin is only allowed when the fingerprint is already verified). It is absent on the initial-handshake send: HandshakeResponse.encode() builds the mysql_clear_password respons…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55856 has been found in org.mariadb.jdbc:mariadb-java-client.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade org.mariadb.jdbc:mariadb-java-client to 2.7.14 or later.
If unsure, ask your IT team or search "org.mariadb.jdbc:mariadb-java-client CVE-2026-55856" on the vendor's site.
CVE-2026-55856 (org.mariadb.jdbc:mariadb-java-client) — CWE-522 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.7.14 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-522) exists in org.mariadb.jdbc:mariadb-java-client.
Check the vendor advisory for the affected versions of org.mariadb.jdbc:mariadb-java-client.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 2.7.14.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.mariadb.jdbc:mariadb-java-client を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.mariadb.jdbc:mariadb-java-client to 2.7.14ステージング環境で 2.7.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。