Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2026-55405

HIGHFix: langchain4j/langchain4j@13a0698

CVE-2026-55405 is a high-severity (CVSS 7.6) SQL Injection vulnerability in dev.langchain4j:langchain4j-mariadb. O3 Security confirms whether CVE-2026-55405 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

LangChain4j: SQL injection via metadata filters in langchain4j-mariadb and langchain4j-pgvector

Also known asGHSA-2mfg-cc43-9pcj
Published
Jul 10, 2026
Updated
Aug 12, 2026
Affected
8 pkgs
Patched
8 / 8
Exploits
None indexed
Exploitation data as of Aug 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-55405.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk
0.00%0.28%0.57%0.85%0.3%0.3%Aug 26Aug 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2026-55405 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 363,908 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

8 pkgs affected
☕dev.langchain4j:langchain4j-mariadb☕dev.langchain4j:langchain4j-mariadb☕dev.langchain4j:langchain4j-mariadb☕dev.langchain4j:langchain4j-mariadb☕dev.langchain4j:langchain4j-pgvector☕dev.langchain4j:langchain4j-pgvector☕dev.langchain4j:langchain4j-pgvector☕dev.langchain4j:langchain4j-pgvector

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

8 total 8 fixed
EcosystemPackageVulnerable rangeFix
☕Mavendev.langchain4j:langchain4j-mariadball versions1.2.1-beta8
☕Mavendev.langchain4j:langchain4j-mariadb≥ 1.3.0-beta9&&< 1.5.1-beta111.5.1-beta11
☕Mavendev.langchain4j:langchain4j-mariadb≥ 1.6.0-beta12&&< 1.11.8-beta191.11.8-beta19
☕Mavendev.langchain4j:langchain4j-mariadb≥ 1.12.1-beta21&&< 1.16.3-beta261.16.3-beta26
☕Mavendev.langchain4j:langchain4j-pgvectorall versions1.2.1-beta8
☕Mavendev.langchain4j:langchain4j-pgvector≥ 1.3.0-beta9&&< 1.5.1-beta111.5.1-beta11

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dev.langchain4j:langchain4j-mariadb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update dev.langchain4j:langchain4j-mariadb to 1.2.1-beta8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-55405 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2026-55405 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-55405. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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
O3 Security · Impact-Aware SCA

Is CVE-2026-55405 in your dependencies?

O3 detects CVE-2026-55405 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works