PT-2026-83375 · Mariadb · Mariadb-Connector-R2Dbc

CVE-2026-55859

·

Published

2026-08-28

·

Updated

2026-08-29

CVSS v3.1

5.9

Medium

VectorAV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Name of the Vulnerable Software and Affected Versions MariaDB Connector/R2DBC versions prior to 1.4.1
Description The driver encodes and decodes all character data assuming the connection character set is UTF-8. A server can announce a mid-session change to the character set client variable through the OK-packet session-state-tracking mechanism, which can be triggered by server configuration, stored routines, triggers, or a hostile man-in-the-middle server. If the character set is changed to a non-UTF-8 value, the driver continues to use UTF-8 while the server interprets the bytes under a different encoding. This results in silent data corruption and a charset-confusion mismatch, which can bypass byte-wise quoting or escaping and potentially lead to SQL injection.
Recommendations Update to version 1.4.1 or later.

Exploit

Fix

Improper Encoding or Escaping of Output

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-55859
GHSA-5RQC-86VF-G8R2

Affected Products

Mariadb-Connector-R2Dbc