MariaDB Corporation MariaDB Connector/J up to 2.7.13/3.3.4/3.4.2/3.5.8 Client-Side Escaping encoding error

Summaryinfo

A vulnerability was found in MariaDB Corporation MariaDB Connector and J up to 2.7.13/3.3.4/3.4.2/3.5.8. It has been declared as problematic. This affects an unknown function of the component Client-Side Escaping. Executing a manipulation can lead to encoding error. This vulnerability is handled as CVE-2026-55858. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability has been found in MariaDB Corporation MariaDB Connector and J up to 2.7.13/3.3.4/3.4.2/3.5.8 and classified as problematic. This vulnerability affects some unknown processing of the component Client-Side Escaping. The manipulation with an unknown input leads to a encoding error vulnerability. The CWE definition for the vulnerability is CWE-172. The product does not properly encode or decode the data, resulting in unexpected values. As an impact it is known to affect integrity. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-55858 since 06/17/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.

Upgrading to version 2.7.14, 3.3.5, 3.4.3 or 3.5.9 eliminates this vulnerability.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Database Software

Vendor

• MariaDB Corporation

Name

• J
• MariaDB Connector

Version

• 2.7.0
• 2.7.1
• 2.7.2
• 2.7.3
• 2.7.4
• 2.7.5
• 2.7.6
• 2.7.7
• 2.7.8
• 2.7.9
• 2.7.10
• 2.7.11
• 2.7.12
• 2.7.13
• 3.3.0
• 3.3.1
• 3.3.2
• 3.3.3
• 3.3.4
• 3.4.0
• 3.4.1
• 3.4.2
• 3.5.0
• 3.5.1
• 3.5.2
• 3.5.3
• 3.5.4
• 3.5.5
• 3.5.6
• 3.5.7
• 3.5.8

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion