CVE-2026-41705 is a high-severity (CVSS 8.6) Expression Language Injection vulnerability in org.springframework.ai:spring-ai-milvus-store. A fix is available for org.springframework.ai:spring-ai-milvus-store — see the affected versions and patch details below.
Spring AI's MilvusVectorStore#doDelete(List) implementation is vulnerable to filter-expression injection via unsanitized document IDs
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41705.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.ai:spring-ai-milvus-store☕org.springframework.ai:spring-ai-milvus-store☕org.springframework.ai:spring-ai-typesense-store☕org.springframework.ai:spring-ai-typesense-storeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.ai:spring-ai-milvus-store | ≥ 1.0.0&&< 1.0.7 | 1.0.7org.springframework.ai:spring-ai-milvus-store:1.0.7 |
| ☕Maven | org.springframework.ai:spring-ai-milvus-store | ≥ 1.1.0&&< 1.1.6 | 1.1.6org.springframework.ai:spring-ai-milvus-store:1.1.6 |
| ☕Maven | org.springframework.ai:spring-ai-typesense-store | ≥ 1.0.0&&< 1.0.7 | 1.0.7org.springframework.ai:spring-ai-typesense-store:1.0.7 |
| ☕Maven | org.springframework.ai:spring-ai-typesense-store | ≥ 1.1.0&&< 1.1.6 | 1.1.6org.springframework.ai:spring-ai-typesense-store:1.1.6 |
Affected Products
spring aivmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.ai:spring-ai-milvus-store, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.ai:spring-ai-milvus-store to 1.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41705 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2026-41705 in your dependencies?
Find it across Maven, including transitive dependencies.