MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing
CVE-2026-119281GHSA-grfq-r75j-rw9x
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.mariadb.jdbc:mariadb-java-client 3.5.11, 3.4.5, 3.3.7), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.mariadb.jdbc:mariadb-java-client
- Affected
- >= 3.0.0, < 3.3.7>= 3.4.0, < 3.4.5>= 3.5.0, < 3.5.11
- Fixed in
- 3.5.11, 3.3.7, 3.4.5
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-grfq-r75j-rw9x lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=3.0.0 =3.4.0 =3.5.0 <3.5.11
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-grfq-r75j-rw9x lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=3.0.0 =3.4.0 =3.5.0 <3.5.11 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
- EPSS
- CVE-2026-119281: 0.28% estimated exploitation activity in the next 30 days; percentile 20.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary MariaDB Connector/J decodes every result as UTF-8 and guards `character_set_client` against a change to another charset, but did not guard `character_set_results`, and relied on the server's global `session_track_system_variables` list to be told about charset changes at all.
Details The connector learns about session variable changes through session tracking, and closes the connection when `character_set_client` is switched away from UTF-8, so that its UTF-8 decoding stays correct. Two gaps remained: - `character_set_results` was not guarded: a server could switch it to another charset, after which the bytes of every result were decoded as UTF-8 although encoded otherwise. - the list of tracked variables came from the server's global `session_track_system_variables`: a server configured, or made, not to track the character set variables could change them silently. The fix requests an explicit session tracking list that includes both character set variables whatever the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-grfq-r75j-rw9x
- Revision 1 · created ·
Published from ghsa record GHSA-grfq-r75j-rw9x
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-119281 Advisory: MariaDB Connector/J: Server could switch character_set_results away from UTF-8 without the client noticing IDs: CVE-2026-119281, GHSA-grfq-r75j-rw9x Record: https://patchnext.com/advisories/cve-2026-119281 (revision 2, source checked 31 Oct 2026, 07:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.mariadb.jdbc:mariadb-java-client 3.5.11, 3.4.5, 3.3.7. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.mariadb.jdbc:mariadb-java-client: affected >= 3.0.0, < 3.3.7; >= 3.4.0, < 3.4.5; >= 3.5.0, < 3.5.11; fixed in 3.5.11, 3.3.7, 3.4.5 ## Suggested inspection (read-only) - Maven org.mariadb.jdbc:mariadb-java-client: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.mariadb.jdbc:mariadb-java-client. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-grfq-r75j-rw9x (GitHub-reviewed advisory GHSA-grfq-r75j-rw9x lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=3.0.0 =3.4.0 =3.5.0 <3.5.11) - Verified: https://osv.dev/vulnerability/GHSA-grfq-r75j-rw9x (OSV record GHSA-grfq-r75j-rw9x lists affected ranges: Maven org.mariadb.jdbc:mariadb-java-client >=3.0.0 =3.4.0 =3.5.0 <3.5.11 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…