Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-v632-2m87-7469

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

CVSS 8.6 HighEPSS 0.0035 · 29th percentile

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.

PackageEcosystemAffectedFixed in
org.springframework.ai:spring-ai-milvus-storeMaven>=1.0.0, <1.0.7 || >=1.1.0, <1.1.61.0.7, 1.1.6
org.springframework.ai:spring-ai-typesense-storeMaven>=1.0.0, <1.0.7 || >=1.1.0, <1.1.61.0.7, 1.1.6
Identifiers
GHSA-v632-2m87-7469 · CVE-2026-41705
Weakness (CWE)
CWE-917
Tags
Published
9 May 2026
Updated
14 May 2026

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

ScoreRatingCVSSVectorSource
8.6 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L 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

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

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.