LangChain4j Metadata Filter EmbeddingSearchRequest.filter injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.65- |
Summary
A vulnerability classified as critical has been found in LangChain4j up to 1.2.1-beta7/1.5.1-beta10/1.11.8-beta18/1.16.3-beta25. This affects the function EmbeddingSearchRequest.filter of the component Metadata Filter Handler. The manipulation leads to injection.
This vulnerability is documented as CVE-2026-55405. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in LangChain4j up to 1.2.1-beta7/1.5.1-beta10/1.11.8-beta18/1.16.3-beta25. It has been rated as critical. This issue affects the function EmbeddingSearchRequest.filter of the component Metadata Filter Handler. The manipulation with an unknown input leads to a injection vulnerability. Using CWE to declare the problem leads to CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-55405 since 06/16/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1055 for this issue.
Upgrading to version 1.2.1-beta8, 1.5.1-beta11, 1.11.8-beta19 or 1.16.3-beta26 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 1.2.1-beta1
- 1.2.1-beta2
- 1.2.1-beta3
- 1.2.1-beta4
- 1.2.1-beta5
- 1.2.1-beta6
- 1.2.1-beta7
- 1.5.1-beta10
- 1.11.8-beta18
- 1.16.3-beta25
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: InjectionCWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: LangChain4j 1.2.1-beta8/1.5.1-beta11/1.11.8-beta19/1.16.3-beta26
Timeline
06/16/2026 CVE reserved07/10/2026 Advisory disclosed
07/10/2026 VulDB entry created
07/10/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-55405 (🔒)
GCVE (CVE): GCVE-0-2026-55405
GCVE (VulDB): GCVE-100-377621
Entry
Created: 07/10/2026 22:59Changes: 07/10/2026 22:59 (53)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.