Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55859 medium CVSS 5.9

Vulnerability in org.mariadb:r2dbc-mariadb (CVE-2026-55859)

Summary

Vulnerability in org.mariadb:r2dbc-mariadb (CVE-2026-55859). Data can be tampered with by attackers. Mitigation: upgrade to 1.4.1 or later.

Original description

The description as published by the source.

Summary

The connector encodes and decodes all character data assuming the connection character set is UTF-8. A server can change character_set_client 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 character_set_client 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 primitive that can defeat byte-wise quoting/escaping when client and server disagree on a multi-byte encoding.

Am I affected?

You are affected if you use mariadb Connector/R2DBC (org.mariadb:r2dbc-mariadb) below 1.4.1 and a connection can be steered, by a hostile or man-in-the-middle server, or by server-side state such as a stored routine, trigger, or configuration — to switch character_set_client to a non-UTF-8 value mid-session.

Impact

Silent data corruption and a client…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55859 has been found in org.mariadb:r2dbc-mariadb.
Data can be tampered with by attackers. CVSS score: 5.9/10.
What to do: upgrade org.mariadb:r2dbc-mariadb to 1.4.1 or later.
If unsure, ask your IT team or search "org.mariadb:r2dbc-mariadb CVE-2026-55859" on the vendor's site.

CVE-2026-55859 (org.mariadb:r2dbc-mariadb) — CWE-116 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.4.1 — apply immediately
Workaround: There is no reliable application-level workaround; upgrade to 1.4.1 or later.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-116) exists in org.mariadb:r2dbc-mariadb.

📍 Affected scope

Check the vendor advisory for the affected versions of org.mariadb:r2dbc-mariadb.

🔥 Severity

Severity: Medium (CVSS 5.9/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.4.1.

🛡️ Workaround

Workaround: There is no reliable application-level workaround; upgrade to 1.4.1 or later.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.mariadb:r2dbc-mariadb を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply temporary workaround mitigate 
    There is no reliable application-level workaround; upgrade to 1.4.1 or later.

    パッチが適用されるまでの応急処置として、There is no reliable application-level workaround; upgrade to 1.4.1 or later. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade org.mariadb:r2dbc-mariadb to 1.4.1

    ステージング環境で 1.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.mariadb:r2dbc-mariadb
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details