Bug 2563687 (CVE-2026-119281) - CVE-2026-119281 org.mariadb.jdbc/mariadb-java-client: mariadb-connector-j: Security feature bypass via unvalidated character set changes
Summary: CVE-2026-119281 org.mariadb.jdbc/mariadb-java-client: mariadb-connector-j: Se...
Keywords:
Status: NEW
Alias: CVE-2026-119281
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-29 21:14 UTC by OSIDB Bzimport
Modified: 2026-11-02 08:09 UTC (History)
46 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-29 21:14:12 UTC
MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, the connector assumed result bytes were UTF-8 but guarded only changes to character_set_client. It did not reject non-UTF-8 character_set_results changes and relied on the server's global session_track_system_variables configuration to report character-set changes. A malicious or compromised server, or a machine-in-the-middle attacker, could suppress tracking or change the result charset so application strings differed from the returned bytes, potentially defeating application-side validation or escaping that depended on the decoded values. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.


Note You need to log in before you can comment on or make changes to this bug.