Advisory record · GHSA-xvr9-35cr-46v9

org.mariadb.jdbc:mariadb-java-client has Inappropriate Encoding for Output Context

CVSS 5.9 MediumEPSS 0.0087 · 59th percentile

Published by the GitHub Advisory Database at 28 Aug 2026, 22:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.mariadb.jdbc:mariadb-java-clientMaven<2.7.14 || >=3.0.0, <3.3.5 || >=3.4.0, <3.4.3 || >=3.5.0, <3.5.92.7.14, 3.3.5, 3.4.3, 3.5.9
Identifiers
GHSA-xvr9-35cr-46v9 · CVE-2026-55858
Weakness (CWE)
CWE-838
Published
28 Aug 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of org.mariadb.jdbc:mariadb-java-client before 2.7.14, from 3.0.0 before 3.3.5, from 3.4.0 before 3.4.3, and from 3.5.0 before 3.5.9 are affected. The driver assumes UTF-8 for all character data, but a server can switch the session to a non-UTF-8 character set mid-session, causing silent data corruption and possibly SQL injection through charset confusion. Upgrade to 2.7.14, 3.3.5, 3.4.3, or 3.5.9 for your branch. The source states there is no reliable application-level workaround.

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

ScoreRatingCVSSVectorSource
5.9 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0087, the 59th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

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.