← Back
CVE-2026-55860
medium
CVSS 5.9
Vulnerability in org.mariadb:r2dbc-mariadb (CVE-2026-55860)
Summary
vulnerability in org.mariadb:r2dbc-mariadb (CVE-2026-55860). Confidential information can be exposed externally. Mitigation: upgrade to `1.4.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55860** has been found in org.mariadb:r2dbc-mariadb.
Confidential information can be exposed externally. 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-55860" on the vendor's site.
CVE-2026-55860 (org.mariadb:r2dbc-mariadb) — CWE-319 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `1.4.1` — apply immediately
Workaround: Until you can upgrade, configure certificate verification explicitly: provide the server/CA certificate and use a verifying SSL mode (e.g.
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-319) exists in org.mariadb:r2dbc-mariadb.
📍 Affected scope
org.mariadb:r2dbc-mariadb — .
🔥 Severity
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.4.1**.
🛡️ Workaround
Workaround: Until you can upgrade, configure certificate verification explicitly: provide the server/CA certificate and use a verifying SSL mode (e.g.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.mariadb:r2dbc-mariadb' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.mariadb:r2dbc-mariadb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.mariadb:r2dbc-mariadb` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Until you can upgrade, configure certificate verification explicitly: provide the server/CA certificate and use a verifying SSL mode (e.g.パッチが適用されるまでの応急処置として、Until you can upgrade, configure certificate verification explicitly: provide the server/CA certificate and use a verifying SSL mode (e.g. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade org.mariadb:r2dbc-mariadb to 1.4.1ステージング環境で 1.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.mariadb:r2dbc-mariadb
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.1"}]}]