Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 29 Oct 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mariadb
Mariadb mariadb-connector-j Mariadb-corporation Mariadb-corporation mariadb-connector-j |
|
| Vendors & Products |
Mariadb
Mariadb mariadb-connector-j Mariadb-corporation Mariadb-corporation mariadb-connector-j |
Thu, 29 Oct 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing | |
| Weaknesses | CWE-838 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-29T20:58:39.322Z
Reserved: 2026-10-29T18:50:28.064Z
Link: CVE-2026-119281
No data.
Status : Received
Published: 2026-10-29T21:17:21.710
Modified: 2026-10-29T21:17:21.710
Link: CVE-2026-119281
No data.
OpenCVE Enrichment
Updated: 2026-10-29T22:30:12Z