CVE-2026-55405

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.6
EG Score
7.6(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
27.3%
KEV
Not listed

Published

June 17, 2026

Last Modified

July 13, 2026

Advisory Details (7)

Auto-updated Jul 10, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

SQL injection via metadata filters in langchain4j-mariadb and langchain4j-pgvector · Advisory · langchain4j/langchain4j · GitHub

https://github.com/langchain4j/langchain4j/security/advisories/GHSA-2mfg-cc43-9pcj
github_release Patch Available

1.16.3 and 1.16.3-beta26

Patch available: langchain4j/langchain4j 1.16.3

https://github.com/langchain4j/langchain4j/releases/tag/1.16.3
github_commit

commit f14a10ce77e4 (langchain4j/langchain4j)

Fix landed in langchain4j/langchain4j commit f14a10ce77e4 — awaiting tagged release

https://github.com/langchain4j/langchain4j/commit/f14a10ce77e4ea1b8277f67d6a81f46abd7a5bc2
github_commit Patch Available

commit ce96291dfb24 (langchain4j/langchain4j)

Patch available: langchain4j/langchain4j 1.17.0 (contains commit ce96291dfb24)

https://github.com/langchain4j/langchain4j/commit/ce96291dfb243c7f6753b5d65c7a77914642314f
github_commit

commit 8805d5d12869 (langchain4j/langchain4j)

Fix landed in langchain4j/langchain4j commit 8805d5d12869 — awaiting tagged release

https://github.com/langchain4j/langchain4j/commit/8805d5d128694302f1b0a2650174186862f669e7
github_commit

commit 1bc1f60aa58e (langchain4j/langchain4j)

Fix landed in langchain4j/langchain4j commit 1bc1f60aa58e — awaiting tagged release

https://github.com/langchain4j/langchain4j/commit/1bc1f60aa58ef5c3c1703caf73362482480351cf
github_commit Patch Available

commit 13a0698bdfaf (langchain4j/langchain4j)

Patch available: langchain4j/langchain4j 1.16.3 (contains commit 13a0698bdfaf)

https://github.com/langchain4j/langchain4j/commit/13a0698bdfaf105d8aaf0367881df51358596219

Vendor Advisories for CVE-2026-55405(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
dev.langchain4j:langchain4j-mariadb1.12.1-beta21 ... 1.16.2-beta26 (11 versions)1.16.3-beta26
dev.langchain4j:langchain4j-pgvector1.12.1-beta21 ... 1.16.2-beta26 (11 versions)1.16.3-beta26

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:20 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-13 22:31 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-06-17 18:44 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55405?
CVE-2026-55405 is a high vulnerability published on June 17, 2026. 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…
When was CVE-2026-55405 disclosed?
CVE-2026-55405 was first published in the National Vulnerability Database on June 17, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55405 actively exploited?
CVE-2026-55405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55405?
CVE-2026-55405 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-55405?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55405, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55405

Explore →

Is Your Infrastructure Affected by CVE-2026-55405?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.