org.mariadb:r2dbc-mariadb has Inappropriate Encoding for Output Context and Improper Encoding or Escaping of Output
CVE-2026-55859GHSA-5rqc-86vf-g8r2
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.mariadb:r2dbc-mariadb 1.4.1), 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:r2dbc-mariadb
- Affected
- < 1.4.1
- Fixed in
- 1.4.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-5rqc-86vf-g8r2 lists affected ranges: Maven org.mariadb:r2dbc-mariadb >=0 <1.4.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-5rqc-86vf-g8r2 lists affected ranges: Maven org.mariadb:r2dbc-mariadb >=0 <1.4.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
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-55859: 0.49% estimated exploitation activity in the next 30 days; percentile 41.95 (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 The connector encodes and decodes all character data assuming the connection character set is UTF-8. A server can change charactersetclient mid-session to a non-UTF-8 charset, after which the driver and server interpret the same bytes under different encodings, causing silent data corruption and a client/server charset-confusion mismatch. Details The driver encodes and decodes all character data on the assumption that the connection character set is UTF-8. The server can, however, announce a change of charactersetclient mid-session through the OK-packet session-state-tracking mechanism, for example via a SET NAMES … run by a stored routine or trigger, by server configuration, or by a hostile server. If the new charset is not UTF-8, the driver continues to read and write UTF-8 while the server interprets the same bytes under a different encoding. The result is silent data corruption and a client/server charset-confusion mismatch. Charset confusion of this kind is also the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-5rqc-86vf-g8r2
- Revision 1 · created ·
Published from osv record GHSA-5rqc-86vf-g8r2
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-55859 Advisory: org.mariadb:r2dbc-mariadb has Inappropriate Encoding for Output Context and Improper Encoding or Escaping of Output IDs: CVE-2026-55859, GHSA-5rqc-86vf-g8r2 Record: https://patchnext.com/advisories/cve-2026-55859 (revision 2, source checked 26 Oct 2026, 16:55 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:r2dbc-mariadb 1.4.1. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.mariadb:r2dbc-mariadb: affected < 1.4.1; fixed in 1.4.1 ## Suggested inspection (read-only) - Maven org.mariadb:r2dbc-mariadb: 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:r2dbc-mariadb. - 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://osv.dev/vulnerability/GHSA-5rqc-86vf-g8r2 (OSV record GHSA-5rqc-86vf-g8r2 lists affected ranges: Maven org.mariadb:r2dbc-mariadb >=0 <1.4.1 (fixed)) - Verified: https://github.com/advisories/GHSA-5rqc-86vf-g8r2 (GitHub-reviewed advisory GHSA-5rqc-86vf-g8r2 lists affected ranges: Maven org.mariadb:r2dbc-mariadb >=0 <1.4.1) Commands are suggestions: review each one before running it.
Loading voting…