CVE-2026-59442
Patch Available.
This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.
Overview
Spring AI is a Spring project that provides a Spring-friendly API and abstractions for developing AI applications, including a portable vector store API with metadata filter expressions that each store implementation translates into its native query syntax.
An authorization bypass vulnerability (CVE-2026-59442) has been identified in the Spring AI Typesense vector store, which allows attackers to retrieve documents outside the scope that an application's filter expression is meant to enforce. When the same filter is used for a delete operation, documents outside the intended scope can also be removed.
Per OWASP: Access control enforces policy such that users cannot act outside of their intended permissions. Failures typically lead to unauthorized information disclosure, modification, or destruction of all data or performing a business function outside the user's limits.
This issue affects multiple versions of Spring AI.
Details
Module Info
- Product: Spring AI
- Affected packages:
org.springframework.ai:spring-ai-typesense-store - Affected versions: >=1.0.0 <=1.0.10, >=1.1.0 <=1.1.9, >=2.0.0 <=2.0.2
- GitHub repository: https://github.com/spring-projects/spring-ai
- Published packages: https://central.sonatype.com/artifact/org.springframework.ai/spring-ai-typesense-store
- Package manager: Maven
- Fixed in:
- OSS Spring AI 2.0.3
- NES for Spring AI
Vulnerability Info
This High-severity vulnerability is found in the org.springframework.ai:spring-ai-typesense-store package in multiple versions of Spring AI. TypesenseVectorStore converts the portable Filter.Expression of a similarity search request, or of a filter-based delete, into a Typesense filter_by string with TypesenseFilterExpressionConverter. The converter writes a binary expression as its left operand, the operator symbol (&& or ||) and its right operand, and it never writes parentheses. Its handling of a parenthesized Filter.Group does not restore them either:
@Override
protected void doExpression(Filter.Expression exp, StringBuilder context) {
this.convertOperand(exp.left(), context);
context.append(getOperationSymbol(exp));
this.convertOperand(exp.right(), context);
}
@Override
protected void doGroup(Filter.Group group, StringBuilder context) {
this.convertOperand(new Filter.Expression(Filter.ExpressionType.AND, group.content(), group.content()),
context); // trick
}A group is rendered as its content joined to itself with &&, with no boundary around it. Typesense evaluates && and || with equal precedence, from left to right, so the string it receives no longer has the meaning the application defined. For example, an application that scopes a search to one tenant with tenant == 'A' && (category == 'a' || category == 'b') produces a filter that is evaluated as (((tenant A && category a) || category b) && category a) || category b, which matches every document in category b regardless of its tenant. An application that relies on grouped filter expressions for tenant isolation or access control can therefore return documents to a remote user that the user should not be able to read, and a delete call that uses the same filter can remove documents outside the intended scope.
Mitigation
Only recent versions of Spring AI receive community support. Older lines are End-of-Life and will not receive public updates to address this issue.
Users of the affected components should apply one of the following mitigations:
- Upgrade to a currently supported version of Spring AI.
- Leverage a commercial support partner like HeroDevs for post-EOL security support.
Credits
Raphael Zanarelli (finder)