CVE-2026-55405

Name of the Vulnerable Software and Affected Versions langchain4j-mariadb versions prior to 1.2.1-beta8 langchain4j-mariadb versions prior to 1.5.1-beta11 langchain4j-mariadb versions prior to 1.11.8-beta19 langchain4j-mariadb versions prior to 1.16.3-beta26 langchain4j-pgvector versions prior to 1.2.1-beta8 langchain4j-pgvector versions prior to 1.5.1-beta11 langchain4j-pgvector versions prior to 1.11.8-beta19 langchain4j-pgvector versions prior to 1.16.3-beta26

Description 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 statements executed by the stores' search and removeAll(Filter) operations. This can lead to blind data exfiltration, denial of service via sleep functions, and deletion of arbitrary rows. In pgvector JSON mode, the JSONFilterMapper places the key inside a single-quoted SQL literal without escaping. In pgvector column mode, the ColumnFilterMapper uses the key as a bare, unquoted SQL identifier. In MariaDB JSON mode, the JSONFilterMapper places the key inside a JSON path literal unescaped, and the MariaDbFilterMapper.formatValue() function fails to escape backslashes. In MariaDB column mode, the ColumnFilterMapper uses the raw, unescaped key when the driver cannot quote it as an identifier.

Recommendations Update langchain4j-mariadb to version 1.2.1-beta8, 1.5.1-beta11, 1.11.8-beta19, or 1.16.3-beta26. Update langchain4j-pgvector to version 1.2.1-beta8, 1.5.1-beta11, 1.11.8-beta19, or 1.16.3-beta26. Do not pass untrusted input as metadata filter keys. Restrict filter keys to a known allow-list at the application layer.