Categories
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.

Original description

The description as published by the source.

LangChain4j is a Java library for building LLM-powered applications on the JVM. Prior to 1.2.1-beta8, 1.5.1-beta11, 1.11.8-beta19, and 1.16.3-beta26, the MariaDB and pgvector embedding stores build metadata-filter SQL by string-concatenating filter keys, and in MariaDB string values, directly into the query without adequate escaping. A crafted metadata key in EmbeddingSearchRequest.filter() can break out of its SQL context and inject arbitrary SQL into the statements executed by the stores' search and removeAll(Filter) operations, enabling blind data exfiltration, denial of service via sleep functions, and deletion of arbitrary rows through removeAll(Filter). This issue is fixed in langchain4j-mariadb and langchain4j-pgvector versions 1.2.1-beta8, 1.5.1-beta11, 1.11.8-beta19, and 1.16.3-beta26.

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-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.

📍 Affected scope

Check the vendor advisory for the affected versions of 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. 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・依存マニフェストで dev.langchain4j:langchain4j-mariadb を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade dev.langchain4j:langchain4j-mariadb to 1.16.3-beta26

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

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

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

Affected packages

maven dev.langchain4j:langchain4j-mariadb
[{"type":"ECOSYSTEM","events":[{"introduced":"1.12.1-beta21"},{"fixed":"1.16.3-beta26"}]}]
maven dev.langchain4j:langchain4j-pgvector
[{"type":"ECOSYSTEM","events":[{"introduced":"1.12.1-beta21"},{"fixed":"1.16.3-beta26"}]}]

References

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