Insufficiently Protected Credentials Affecting org.mariadb.jdbc:mariadb-java-client package, versions [,2.7.14)[3.0.0,3.3.5)[3.4.0,3.4.3)[3.5.0,3.5.9)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGMARIADBJDBC-19428608
- published29 Aug 2026
- disclosed28 Aug 2026
- creditUnknown
Introduced: 28 Aug 2026
NewCVE-2026-55856 (opens in a new tab)How to fix?
Upgrade org.mariadb.jdbc:mariadb-java-client to version 2.7.14, 3.3.5, 3.4.3, 3.5.9 or higher.
Overview
Affected versions of this package are vulnerable to Insufficiently Protected Credentials in the initial-handshake process. An attacker can intercept and obtain database credentials by performing a man-in-the-middle attack during the authentication exchange when the connection is established with TLS verification enabled but without a pinned server certificate. This is only exploitable if the client is configured with sslMode=verify-full or verify-ca, uses a password, and does not pin the server certificate.
Workaround
This vulnerability can be mitigated by pinning the server certificate (setting serverSslCert to the real CA or server certificate), which will cause the client to reject untrusted certificates before any credentials are transmitted.