CVE-2026-55858

Medium

Description

MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. Prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9, the connector encodes and decodes protocol text and performs client-side escaping under the assumption that the connection character set is UTF-8. The server can report a mid-session change to character_set_client through OK-packet session-state tracking, including a change caused by SET NAMES, a stored routine or trigger, server configuration, or a hostile server. If character_set_client changes to a non-UTF-8 value, the driver continues to read and write UTF-8 while the server interprets the same bytes under another encoding, causing silent data corruption and a client/server charset-confusion mismatch that can defeat byte-wise quoting or escaping. The fix accepts only utf8, utf8mb3, or utf8mb4 after initialization; any other value causes SQLException with SQLState 08000 and closes the connection. This issue is fixed in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9.

SeverityMedium
CVSS5.9
Exploit probability—
ProductOrg.mariadb.jdbc:mariadb-java-client
PublishedAug 28, 2026
First seenAug 28, 2026
Weakness typeCWE-838CWE-838

How to fix

Update
  • org.mariadb.jdbc:mariadb-java-client2.7.14, 3.3.5, 3.4.3, 3.5.9 or later

Affected products

ProductAffected versionsFixed in
org.mariadb.jdbc:mariadb-java-clientMavenv < 2.7.14, 3.0.0 ≤ v < 3.3.5, 3.4.0 ≤ v < 3.4.3, 3.5.0 ≤ v < 3.5.92.7.14, 3.3.5, 3.4.3, 3.5.9

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.