# Spring AI's MilvusVectorStore#doDelete(List) implementation is vulnerable to filter-expression injection via unsanitized document IDs

Advisory record · `GHSA-v632-2m87-7469`

- **Identifiers:** `GHSA-v632-2m87-7469` · `CVE-2026-41705`
- **State:** Confirmed
- **Severity:** CVSS 8.6 High
- **Critical:** No
- **Weakness (CWE):** [CWE-917](https://cwe.mitre.org/data/definitions/917.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Published:** 9 May 2026
- **Updated:** 14 May 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 May 2026, 03:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.springframework.ai:spring-ai-milvus-store` (Maven): affected `>=1.0.0, <1.0.7 || >=1.1.0, <1.1.6`; fixed in `1.0.7`, `1.1.6`
- `org.springframework.ai:spring-ai-typesense-store` (Maven): affected `>=1.0.0, <1.0.7 || >=1.1.0, <1.1.6`; fixed in `1.0.7`, `1.1.6`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Spring AI's spring-ai-milvus-store package, versions 1.0.0 to before 1.0.7 and 1.1.0 to before 1.1.6, is vulnerable to filter-expression injection through unsanitized document IDs passed to the delete operation. The source does not state what access an attacker needs to exploit this or the full impact. The spring-ai-typesense-store package is also listed with the same affected and fixed versions, but the source gives no details on it. Upgrade spring-ai-milvus-store to 1.0.7 or 1.1.6, and upgrade spring-ai-typesense-store to the same versions.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.6 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`, from CNA (vmware)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0035, the 29th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-v632-2m87-7469)

## Sources

- [GitHub Advisory Database: GHSA-v632-2m87-7469](https://github.com/advisories/GHSA-v632-2m87-7469)
- [OSV: GHSA-v632-2m87-7469](https://osv.dev/vulnerability/GHSA-v632-2m87-7469)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-41705>
- <https://github.com/spring-projects/spring-ai/pull/6011>
- <https://github.com/spring-projects/spring-ai>
- <https://spring.io/security/cve-2026-41705>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-v632-2m87-7469>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-v632-2m87-7469/>. Everything for agents: <https://agentprime.io/llms.txt>.