# MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing Advisory record · `GHSA-grfq-r75j-rw9x` - **Identifiers:** `GHSA-grfq-r75j-rw9x` · `CVE-2026-119281` - **State:** Confirmed - **Severity:** CVSS 5.9 Medium - **Critical:** No - **Weakness (CWE):** [CWE-838](https://cwe.mitre.org/data/definitions/838.html) - **Tags:** [CWE-838](https://agentprime.io/advisories/tag/cwe-838.md) - **Published:** 30 Oct 2026 - **Updated:** 30 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 30 Oct 2026, 22:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.mariadb.jdbc:mariadb-java-client` (Maven): affected `>=3.0.0, <3.3.7 || >=3.4.0, <3.4.5 || >=3.5.0, <3.5.11`; fixed in `3.3.7`, `3.4.5`, `3.5.11` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > MariaDB Connector/J versions 3.0.0 through 3.3.6, 3.4.0 through 3.4.4, and 3.5.0 through 3.5.10 can decode query results as UTF-8 even when the server has switched character_set_results to another charset. An attacker who controls the database server or sits in a man-in-the-middle position on the connection could alter the strings an application reads, which may defeat validation or escaping. Upgrade to 3.3.7, 3.4.5, 3.5.11, or later. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 5.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0028, the 20th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 29 Oct 2026, 20:58 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-119281) - 29 Oct 2026, 21:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-119281) - 31 Oct 2026, 14:16 UTC: First seen by agentprime - 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-grfq-r75j-rw9x) ## Sources - [GitHub Advisory Database: GHSA-grfq-r75j-rw9x](https://github.com/advisories/GHSA-grfq-r75j-rw9x) - [OSV: GHSA-grfq-r75j-rw9x](https://osv.dev/vulnerability/GHSA-grfq-r75j-rw9x) - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .