{"answers":{"affected":"2 open source packages ship an affected version, including org.mariadb:r2dbc-mariadb.","exploited":"There is no known exploitation of CVE-2026-55859 in the wild and no public exploit code.","fix":"Upgrade org.mariadb:r2dbc-mariadb to 1.4.1 or later.","what":"CVE-2026-55859 is a medium-severity vulnerability in mariadb-corporation mariadb-connector-r2dbc, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55859 and fix it if it is affected.\n\nWhat it is: CVE-2026-55859 is a medium-severity vulnerability in mariadb-corporation mariadb-connector-r2dbc, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-55859 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.mariadb:r2dbc-mariadb (Maven): affected all versions; fixed in 1.4.1\n- org.mariadb:r2dbc-mariadb (Maven): affected all versions; fixed in 1.4.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-55859/ (Markdown: https://insights.sbomify.com/CVE-2026-55859/index.md)","id":"CVE-2026-55859","markdown":"https://insights.sbomify.com/CVE-2026-55859/index.md","name":"CVE-2026-55859","record":{"aliases":["GHSA-5rqc-86vf-g8r2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MariaDB R2DBC connector","requires_auth":"none","summary":"A character set mismatch in the MariaDB R2DBC connector allows silent data corruption and bypasses escaping mechanisms, potentially leading to security issues.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-838","name":"Inappropriate Encoding for Output Context"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"org.mariadb:r2dbc-mariadb has Inappropriate Encoding for Output Context and Improper Encoding or Escaping of Output","id":"CVE-2026-55859","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"org.mariadb:r2dbc-mariadb vulnerable to cleartext password disclosure to a man-in-the-middle server (clear-text auth plugins not gated on a secure transport)","id":"CVE-2026-55860"},"packages":[{"ecosystem":"Maven","fixed":["1.4.1"],"introduced":["0"],"last_affected":[],"package":"org.mariadb:r2dbc-mariadb","purl":null,"source":"GHSA-5rqc-86vf-g8r2"},{"ecosystem":"Maven","fixed":["1.4.1"],"introduced":["0"],"last_affected":[],"package":"org.mariadb:r2dbc-mariadb","purl":"pkg:maven/org.mariadb/r2dbc-mariadb","source":"GHSA-5rqc-86vf-g8r2"}],"prev":{"headline":"MariaDB Connector/J: Inappropriate Encoding for Output Context in org.mariadb.jdbc:mariadb-java-client","id":"CVE-2026-55858"},"products":["mariadb-connector-r2dbc","r2dbc-mariadb"],"published":"2026-08-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["mariadb-corporation","org.mariadb"]},"summary":"A character set mismatch in the MariaDB R2DBC connector allows silent data corruption and bypasses escaping mechanisms, potentially leading to security issues.","url":"https://insights.sbomify.com/CVE-2026-55859/"}