← Back
CVE-2026-55405
high
CVSS 7.6
SQL Injection in dev.langchain4j:langchain4j-mariadb (CVE-2026-55405)
Summary
SQL injection in dev.langchain4j:langchain4j-mariadb (CVE-2026-55405). Confidential information can be exposed externally. Exploitable via ``COMBINED_JSON``. Mitigation: upgrade to `1.16.3-beta26` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55405** has been found in dev.langchain4j:langchain4j-mariadb.
Attackers can target a specific entry point like ``COMBINED_JSON`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.6/10.
What to do: upgrade dev.langchain4j:langchain4j-mariadb to **1.16.3-beta26** or later.
If unsure, ask your IT team or search "dev.langchain4j:langchain4j-mariadb CVE-2026-55405" on the vendor's site.
CVE-2026-55405 (dev.langchain4j:langchain4j-mariadb) — CWE-89 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `COMBINED_JSON` / `COMBINED_JSONB` / `JSONFilterMapper` / `COLUMN_PER_KEY`
Patched: `1.16.3-beta26` — apply immediately
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
**SQL injection** (CWE-89) exists in dev.langchain4j:langchain4j-mariadb. Attackers reach the vulnerable code path via ``COMBINED_JSON`` without authentication.
📍 Affected scope
dev.langchain4j:langchain4j-mariadb — . Attack surface: `COMBINED_JSON` / `COMBINED_JSONB` / `JSONFilterMapper` / `COLUMN_PER_KEY`.
🔥 Severity
Severity: High (CVSS 7.6/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.16.3-beta26**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'dev.langchain4j:langchain4j-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 'dev.langchain4j:langchain4j-mariadb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `dev.langchain4j:langchain4j-mariadb` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade dev.langchain4j:langchain4j-mariadb to 1.16.3-beta26ステージング環境で 1.16.3-beta26 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
dev.langchain4j:langchain4j-mariadb
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.16.3-beta26"}]}]
maven
dev.langchain4j:langchain4j-pgvector
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.16.3-beta26"}]}]