CVE-2026-41705: VMware Spring AI filter expression injection in MilvusVectorStore

CVE-2026-41705 · Severity: high · CVSS 8.6 · Published 2026-05-09

Spring AI, a framework for integrating artificial intelligence into Java applications, contains a security vulnerability in its Milvus database integration. An attacker can use specially crafted document identifiers to manipulate database queries, potentially leading to unauthorized data access or modification. Organizations using Spring AI with Milvus should upgrade to versions 1.0.7 or 1.1.6 to protect their data and operations.

Technologies: VMware Spring Ai. Vendors: Maven, VMware.

Quick answers

Is CVE-2026-41705 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-41705 being exploited in the wild.
How severe is CVE-2026-41705?
High severity, with a CVSS score of 8.6, published 9 May 2026.
Which products and versions are affected?
org.springframework.ai:spring-ai-milvus-store (Maven) ECOSYSTEM:introduced=1.0.0,fixed=1.0.7; org.springframework.ai:spring-ai-typesense-store (Maven) ECOSYSTEM:introduced=1.0.0,fixed=1.0.7; VMware Spring AI (Milvus Store) 1.0.0 to 1.0.6, 1.1.0 to 1.1.5; VMware Spring AI (Typesense Store) 1.0.0 to 1.0.6, 1.1.0 to 1.1.5; and 1 more.
Is there a fix for CVE-2026-41705?
Yes. org.springframework.ai:spring-ai-milvus-store (Maven): upgrade to 1.0.7 or later; org.springframework.ai:spring-ai-typesense-store (Maven): upgrade to 1.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41705 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-41705?
Check whether you run org.springframework.ai:spring-ai-milvus-store (Maven), org.springframework.ai:spring-ai-typesense-store (Maven), VMware Spring AI (Milvus Store) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.springframework.ai:spring-ai-milvus-store (Maven): upgrade to 1.0.7 or later
    # set org.springframework.ai:spring-ai-milvus-store to 1.0.7 in your pom.xml or build.gradle
  • org.springframework.ai:spring-ai-typesense-store (Maven): upgrade to 1.0.7 or later
    # set org.springframework.ai:spring-ai-typesense-store to 1.0.7 in your pom.xml or build.gradle

Technical details

A filter-expression injection vulnerability (CWE-917) exists in Spring AI's MilvusVectorStore#doDelete(List) implementation. The root cause is the failure to properly sanitize document IDs before they are incorporated into expression language statements used for database operations. A remote attacker can exploit this by providing malicious document IDs that alter the logic of the filter expression. This can result in unauthorized data retrieval, modification, or deletion within the Milvus vector database. The vulnerability is addressed in Spring AI versions 1.0.7 and 1.1.6.

Affected products

  • VMware Spring AI 1.0.0 to 1.0.6, 1.1.0 to 1.1.5

Identifiers

  • CVE-2026-41705
  • GHSA-v632-2m87-7469

Timeline

  • 2026-05-09: advisory: Initial disclosure by VMware/Spring

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.