Vulnerability in org.springframework.ai:spring-ai-milvus-store (CVE-2026-41705)
Summary
Vulnerability in org.springframework.ai:spring-ai-milvus-store (CVE-2026-41705). Confidential information can be exposed externally. Mitigation: upgrade to 1.1.6 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41705 has been found in org.springframework.ai:spring-ai-milvus-store.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade org.springframework.ai:spring-ai-milvus-store to 1.1.6 or later.
If unsure, ask your IT team or search "org.springframework.ai:spring-ai-milvus-store CVE-2026-41705" on the vendor's site.
CVE-2026-41705 (org.springframework.ai:spring-ai-milvus-store) — CWE-917 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.1.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-917) exists in org.springframework.ai:spring-ai-milvus-store.
Check the vendor advisory for the affected versions of org.springframework.ai:spring-ai-milvus-store.
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.
Update to 1.1.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.springframework.ai:spring-ai-milvus-store を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.springframework.ai:spring-ai-milvus-store to 1.1.6ステージング環境で 1.1.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch security@vmware.com
- web github.com
- web github.com