Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreTypesenseFilterExpressionConverter does not correctly translate grouped (parenthesized) filter expressions into the Typesense filter syntax.
As a result, the filter sent to Typesense can have a different meaning than the one the application defined, and some conditions may not be applied as intended.
An application is affected if it uses the Typesense vector store with filter expressions that contain groups and relies on them to restrict results, for example to enforce tenant isolation or access control. In that case, a remote user may be able to retrieve documents they should not have access to, and the same filter used for a delete operation may remove documents outside the intended scope.
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 an upgrade is not possible, avoid using grouped expressions in filters that carry tenant or authorization constraints, or enforce those constraints separately from the Filter.Expression passed to the Typesense vector store.
The issue was reported responsibly by Raphael Zanarelli - https://github.com/zanarellidev
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy