Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAccess application API endpoint
-
DeliverySubmit crafted document ID with injected filter syntax
-
ExploitTrigger MilvusVectorStore doDelete method
-
ExecutionInjected expression executes in Milvus query
-
ImpactUnauthorized data deletion or information disclosure
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Expression language sanitization
|
| Exploitation Conditions | Exploitation requires applications using Spring AI's MilvusVectorStore component where the doDelete(List) method is invoked with document IDs derived from untrusted sources such as user input, API parameters, or external data feeds. The vulnerability is specific to delete operations on Milvus vector databases-other vector store implementations in Spring AI (Pinecone, Weaviate, Redis, etc.) are not affected by this particular injection flaw. Applications that only use hardcoded or internally-generated document IDs, or that do not expose delete functionality to end users, are not exploitable despite running vulnerable Spring AI versions. The attack requires network access to the application's API or interface that triggers vector store delete operations, but no authentication is required per the CVSS vector (PR:N), meaning publicly-accessible endpoints are at highest risk. |
| Impact | CVSS 8.6 indicates critical severity with remote exploitation requiring no authentication (AV:N/AC:L/PR:N/UI:N), enabling high confidentiality impact and limited integrity/availability impacts. The network attack vector and low complexity suggest ease of exploitation once the attack pattern is understood. However, real-world risk depends heavily on deployment context: this vulnerability only affects applications using Spring AI's MilvusVectorStore with externally-controlled document IDs in delete operations. EPSS and KEV data not provided, suggesting no widespread exploitation detected yet. The Java-specific nature and relatively niche use case (vector database integrations in AI applications) limits attack surface compared to vulnerabilities in core web frameworks. Primary risk is to organizations deploying RAG systems or AI agents that allow user-supplied identifiers for document management operations. The combination of high CVSS but specialized attack surface suggests prioritization should focus on confirming whether MilvusVectorStore delete operations are exposed to untrusted input in your environment. |
| Exploit ScenarioDerived | An attacker identifies a RAG-enabled application using Spring AI's MilvusVectorStore where users can delete their uploaded documents by ID. The attacker crafts a malicious document ID containing Milvus filter expression syntax (e.g., 'valid_id) OR (1==1') and submits it to the delete endpoint. The unsanitized ID is incorporated into the MilvusVectorStore filter expression, causing the injected logic to execute and delete unintended documents across the vector database or exfiltrate metadata about other users' embeddings through filter-based queries. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 09, 2026
Filter-expression injection in Spring AI's MilvusVectorStore allows remote unauthenticated attackers to manipulate vector database queries by injecting malicious filter expressions through unsanitized document IDs. Affects Spring AI 1.0.0-1.0.6 and 1.1.0-1.1.5. VMware has released patches in versions 1.0.7 and 1.1.6. CVSS 8.6 (High) with network attack vector and no privileges required. No active exploitation confirmed (not in CISA KEV) and no public POC identified at time of analysis.
RemediationAI
Upgrade to Spring AI 1.0.7 or later for the 1.0.x branch, or upgrade to Spring AI 1.1.6 or later for the 1.1.x branch, as specified in VMware's security advisory at https://spring.io/security/cve-2026-41705. The patched versions implement proper input sanitization in the MilvusVectorStore doDelete method to prevent filter-expression injection. If immediate patching is not feasible, implement strict input validation on document IDs before passing them to vector store delete operations-specifically, whitelist alphanumeric characters and reject any IDs containing Milvus filter expression metacharacters (parentheses, logical operators, comparison operators). This workaround may break legitimate use cases requiring special characters in document identifiers and should be tested thoroughly. Additionally, apply principle of least privilege to Milvus database credentials used by Spring AI to limit blast radius of successful injection attacks-restrict delete permissions where possible and isolate vector store collections by trust boundary.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Spring AI is VMware's application framework for building AI-powered applications in Java, providing abstractions for vector databases and large language models. The vulnerability exists in the MilvusVectorStore component, which interfaces with Milvus vector databases for similarity search and retrieval-augmented generation (RAG) workflows. The doDelete(List) method fails to sanitize document IDs before incorporating them into filter expressions sent to the Milvus database. This is a CWE-917 (Expression Language Injection) vulnerability where attacker-controlled data is interpreted as executable filter logic rather than literal identifiers. The affected CPE (cpe:2.3:a:spring:spring_ai) indicates this is specific to Spring AI's vector store implementations, not the broader Spring Framework ecosystem.
Know when Spring gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Primary rating from Vendor (vmware) · only source for this CVE.
CVSS VectorVendor: vmware
Lifecycle Timeline
2DescriptionCVE.org
Spring AI's MilvusVectorStore#doDelete(List) implementation is vulnerable to filter-expression injection via unsanitized document IDs. Spring AI 1.0.x: affected from 1.0.0 through latest 1.0.x; upgrade to 1.0.7 or greater. Spring AI 1.1.x: affected from 1.1.0 through latest 1.1.x; upgrade to 1.1.6 or greater.
Blast Radius
ecosystem impact- 2 maven packages depend on org.springframework.ai:spring-ai-milvus-store (1 direct, 1 indirect)
- 1 maven packages depend on org.springframework.ai:spring-ai-typesense-store (1 direct, 0 indirect)
Ecosystem-wide dependent count for version 1.0.0 and other introduced versions.
Executive ViewAI
Spring AI's MilvusVectorStore contains a filter-expression injection vulnerability (CVE-2026-41705) that allows unauthenticated remote attackers to manipulate vector database queries, potentially exposing or corrupting AI-driven search results and data integrity across affected applications. Organizations using Spring AI versions 1.0.0-1.0.6 or 1.1.0-1.1.5 should prioritize patching to prevent unauthorized access to vector-stored data used in production AI systems.
Vendor-released patch: Spring AI 1.0.7 and 1.1.6. Until patching is completed, implement network-level controls to restrict MilvusVectorStore access to trusted internal networks only and apply input validation rules at the application layer to reject document IDs containing filter-expression syntax characters.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Access control bypass in SpringBlade v4.5.0 importUser function allows low-privileged users to import sensitive user dat
Spring Cloud Config Server contains a path traversal vulnerability when using the native file system backend, allowing u
Spring Framework MVC applications can be vulnerable to a “Path Traversal Vulnerability” when deployed on a non-compliant
SpringBlade v4.5.0 has an access control flaw in authRoutes allowing low-privileged users to escalate to admin through t
Remote code execution in Spring for GraphQL versions 1.3.0-1.3.8, 1.4.0-1.4.5, and 2.0.0-2.0.3 allows unauthenticated at
Server-Sent Events (SSE) stream corruption affects Spring MVC applications built on the functional web framework across
Spring AI versions 1.0.0 through 1.0.4 and 1.1.0 through 1.1.3 allow unauthenticated remote code execution through Sprin
Unsafe JSON deserialization in Spring Framework's JMS message converters (MappingJackson2MessageConverter and JacksonJso
Spring Security Aspects may not correctly locate method security annotations on private methods. Rated critical severity
Safety-guard bypass in the Spring Framework SpEL engine (VMware/Broadcom) lets attacker-controlled expression input esca
Directory traversal in Spring Cloud Config server module allows remote unauthenticated attackers to read arbitrary files
Spring Security fails to properly write HTTP response headers in servlet applications across multiple versions (5.7.0-5.
EUVD-2026-28875
GHSA-v632-2m87-7469
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB