MariaDB Connector/R2DBC is a non-blocking MariaDB and MySQL client implemented in Java. Prior to 1.4.1, org.mariadb:r2dbc-mariadb encodes and decodes all character data under the assumption that the connection character set is UTF-8. A server can announce a mid-session change to character_set_client through the OK-packet session-state-tracking mechanism, including through SET NAMES executed by a stored routine or trigger, server configuration, or a hostile or man-in-the-middle server. If the new character set is not UTF-8, the driver continues to exchange UTF-8 while the server interprets the same bytes under a different encoding, causing silent data corruption and a client/server charset-confusion mismatch that can defeat byte-wise quoting or escaping. The fix accepts only utf8, utf8mb3, or utf8mb4 after initialization; any other value raises R2dbcNonTransientResourceException with SQLState 08000 and closes the connection. This issue is fixed in version 1.4.1.
CVE-2026-55859
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(low)
- EG Risk
- 31(Track)EG Risk 31/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity59% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (4)
Auto-updated Aug 28, 2026[R2DBC-124] Ensure a non-UTF8 charset cannot be used for protocol exchanges - Jira
https://jira.mariadb.org/browse/R2DBC-124MariaDB Connector/R2DBC 1.4.1
Patch available: mariadb-corporation/mariadb-connector-r2dbc 1.4.1
https://github.com/mariadb-corporation/mariadb-connector-r2dbc/releases/tag/1.4.1commit 38bad9afebc6 (mariadb-corporation/mariadb-connector-r2dbc)
Patch available: mariadb-corporation/mariadb-connector-r2dbc 1.4.1 (contains commit 38bad9afebc6)
https://github.com/mariadb-corporation/mariadb-connector-r2dbc/commit/38bad9afebc6c581a853656a42f9ebf403b1b1b7Inappropriate Encoding for Output Context and Improper Encoding or Escaping of Output in org.mariadb:r2dbc-mariadb · Advisory · mariadb-corporation/mariadb-connector-r2dbc · GitHub
Affected: 1.4.1. Once the connection is fully initialized, any subsequent charset change to
https://github.com/mariadb-corporation/mariadb-connector-r2dbc/security/advisories/GHSA-5rqc-86vf-g8r2Vendor Advisories for CVE-2026-55859(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 23:24 UTCEG score recompute
- 2026-08-28 23:01 UTCEG score recompute
- 2026-08-28 22:58 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-55859?
When was CVE-2026-55859 disclosed?
Is CVE-2026-55859 actively exploited?
What is the CVSS score of CVE-2026-55859?
How do I remediate CVE-2026-55859?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55859
Is Your Infrastructure Affected by CVE-2026-55859?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.