Vulnerability in org.mariadb.jdbc:mariadb-java-client (CVE-2026-55857)
Summary
Vulnerability in org.mariadb.jdbc:mariadb-java-client (CVE-2026-55857). 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 PAM (dialog) authentication is used, the connector can be coerced into sending the account password in cleartext over an insecure connection. A hostile or man-in-the-middle server can trigger this with the default configuration, disclosing the user's password.
Details
The mysql_clear_password plugin is gated behind a secure connection: the driver refuses to transmit the password in cleartext over plain TCP. The sibling PAM plugin handler (SendPamAuthPacketFactory, server-side plugin name dialog) did not override that gate and inherited the default value false, so it was not subject to the same secure-transport requirement.
As a result, a hostile or man-in-the-middle server can issue an Authentication Switch Request for the dialog plugin over plain TCP, and the driver responds with the user's password in cleartext. With the default configuration (sslMode=DISABLE, restrictedAuth=null) this is reachable with no non-default options.
Am I affected?
You are affected if all of the following hold:
- You use mariadb Connector/J at a version below the patched release(s).
- Connections can occur over an insecure transport — i.e. plain TCP (sslMode=DISABLE), or a TLS mode that establishes server identity only via self-signed-certificate fingerprint validation.
- An attacker can occupy an on-path (MITM) position, or otherwise cause the client to connect to a server they control, and present an Authentication Switch Request for the dialog plugin.
Connection…
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-55857 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-55857" on the vendor's site.
CVE-2026-55857 (org.mariadb.jdbc:mariadb-java-client) — CWE-319 / 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-319) 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 でアラート再発が無いか継続監視。