Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreTypesenseVectorStore is vulnerable to a document ID injection in its delete operation that can cause unintended documents to be deleted.
TypesenseVectorStore.doDelete(List<String>) builds a Typesense filter_by expression by raw string concatenation of caller-supplied document IDs into the form id: [id1,id2,...]. The Typesense id field uses bare (unquoted) values in this list form with no escaping mechanism. An ID containing characters with syntactic meaning in the Typesense filter grammar — such as a comma (,), a closing bracket (]), or operator tokens (||, &&) — can break out of the list literal and alter the structure of the filter expression.
An attacker who controls a document ID passed to the delete operation can use this to delete documents other than the intended ones (comma injection), or to construct a filter that matches every document in the collection (operator breakout), resulting in unintended bulk deletion.
Applications that pass externally supplied or user-controlled document IDs to VectorStore.delete(List<String>) backed by TypesenseVectorStore are affected.
Spring AI:
| Fix version | Availability |
|---|---|
| 2.0.3 | OSS |
| 2.0.2.1 | Enterprise Support Only |
| 1.1.10 | Enterprise Support Only |
| 1.0.11 | Enterprise Support Only |
Users of affected versions should upgrade to the corresponding fixed version.
If upgrading is not immediately possible, validate every document ID before passing it to VectorStore.delete(List<String>) and reject any ID that contains characters outside a known-safe set. A safe set for Typesense bare-value list syntax includes letters, digits, hyphens, underscores, dots, colons, forward slashes, and at-signs. IDs produced by UUID.randomUUID() or standard base64url encoding are safe.
This issue was identified and responsibly reported by Ishaq Mohammed - https://ishaqmohammed.me/ and independently reported by Daehyun Kang @daehyuh and LiZhiyao (BUPT)
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy