Skip to main content

Spring AI EUVDEUVD-2026-28875

| CVE-2026-41705 HIGH
Improper Neutralization of Special Elements used in an Expression Language Statement (CWE-917)
2026-05-09 vmware GHSA-v632-2m87-7469
8.6
CVSS 3.1 · Vendor: vmware
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Access application API endpoint
  2. Delivery
    Submit crafted document ID with injected filter syntax
  3. Exploit
    Trigger MilvusVectorStore doDelete method
  4. Execution
    Injected expression executes in Milvus query
  5. Impact
    Unauthorized 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Spring AI 1.0.0 <1.0.7
Spring AI 1.1.0 <1.1.6

Affected Packages

maven org.springframework.ai:spring-ai-milvus-store fix: 1.0.7, 1.1.6
maven org.springframework.ai:spring-ai-typesense-store fix: 1.0.7, 1.1.6
euvd spring_ai fix: 1.0.7, 1.1.6

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

Vendor (vmware) PRIMARY 8.6 HIGH
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

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

Lifecycle Timeline

2
Patch available
May 09, 2026 - 02:16 EUVD
CVE Published
May 09, 2026 - 00:34 nvd
HIGH 8.6

DescriptionCVE.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
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 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

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.0%
Top 95% exploitable
Threat Intel
1
1 source
Social Media
2
Sightings
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

43
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +43
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

More in Spring

View all
CVE-2025-70982 CRITICAL POC
9.9 Jan 26

Access control bypass in SpringBlade v4.5.0 importUser function allows low-privileged users to import sensitive user dat

CVE-2026-22739 HIGH POC
8.6 Mar 24

Spring Cloud Config Server contains a path traversal vulnerability when using the native file system backend, allowing u

CVE-2025-41242 MEDIUM POC
5.9 Aug 18

Spring Framework MVC applications can be vulnerable to a “Path Traversal Vulnerability” when deployed on a non-compliant

CVE-2025-70983 CRITICAL
9.9 Jan 23

SpringBlade v4.5.0 has an access control flaw in authRoutes allowing low-privileged users to escalate to admin through t

CVE-2026-41699 CRITICAL
9.8 Jun 11

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

CVE-2026-59313 CRITICAL
9.8 Aug 27

Server-Sent Events (SSE) stream corruption affects Spring MVC applications built on the functional web framework across

CVE-2026-22738 CRITICAL
9.8 Mar 27

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

CVE-2026-41855 CRITICAL
9.8 Jun 09

Unsafe JSON deserialization in Spring Framework's JMS message converters (MappingJackson2MessageConverter and JacksonJso

CVE-2025-41232 CRITICAL
9.1 May 21

Spring Security Aspects may not correctly locate method security annotations on private methods. Rated critical severity

CVE-2026-59283 CRITICAL
9.1 Aug 27

Safety-guard bypass in the Spring Framework SpEL engine (VMware/Broadcom) lets attacker-controlled expression input esca

CVE-2026-40982 CRITICAL
9.1 May 07

Directory traversal in Spring Cloud Config server module allows remote unauthenticated attackers to read arbitrary files

CVE-2026-22732 CRITICAL POC
9.1 Mar 19

Spring Security fails to properly write HTTP response headers in servlet applications across multiple versions (5.7.0-5.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy