Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-119281— MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing

Quick assessment

Affected
mariadb-corporation mariadb-connector-j
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

MariaDB Connector/J 用于将 Java 开发的应用程序连接到 MariaDB 和 MySQL 数据库。在 3.0.0 至 3.3.7、3.4.5 和 3.5.11 版本中，该连接器假设结果字节为 UTF-8 编码，但仅对 的变更进行了防护。它并未拒绝非 UTF-8 的 变更，而是依赖服务器端的 全局配置来报告字符集变更。恶意或已被攻陷的服务器，或中间人攻击者，可以抑制该跟踪机制或修改结果字符集，导致应用程序中的字符串与返回的字节不一致，从而可能绕过依赖于解码值的客户端验证或转义机制。该问题已在 3

CVSS 5.9 · Medium
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-119281

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
输出上下文语义编码不恰当
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
mariadb-corporation mariadb-connector-j >= 3.0.0, < 3.3.7 -

II. Public POCs for CVE-2026-119281

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-119281

请登录查看更多情报信息。

Other References for CVE-2026-119281 (7)

Same Patch Batch · mariadb-corporation · 2026-10-29 · 7 CVEs total

CVE-2026-119210 5.9 MEDIUM MariaDB Connector/J: LOAD DATA LOCAL INFILE file check could be satisfied by text inside q
CVE-2026-119276 5.9 MEDIUM MariaDB Connector/J: Rogue server can drive large heap allocations from server-declared le
CVE-2026-119279 5.9 MEDIUM MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated
CVE-2026-119277 5.9 MEDIUM MariaDB Connector/J: Rogue server can make the client read past the packet through server-
CVE-2026-119278 5.9 MEDIUM MariaDB Connector/J: Rogue server can crash the client during caching_sha2_password authen
CVE-2026-119280 3.7 LOW MariaDB Connector/J : XA recover() trusted server-supplied gtrid and bqual lengths

IV. Related Vulnerabilities

Same product: mariadb-connector-j
Same vendor: mariadb-corporation
Same weakness: CWE-838