Answer in brief
CVE-2026-40966 records a Medium severity secret exfiltration vulnerability in Spring AI's VectorStoreChatMemoryAdvisor conversation scoping can lead to cross-tenant memory exfiltration. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
Answer in brief
CVE-2026-40966 records a Medium severity secret exfiltration vulnerability in Spring AI's VectorStoreChatMemoryAdvisor conversation scoping can lead to cross-tenant memory exfiltration. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
Update org.springframework.ai:spring-ai-advisors-vector-store to 1.0.6; org.springframework.ai:spring-ai-advisors-vector-store to 1.1.5 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSecret Exfiltration describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-40966 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| org.springframework.ai:spring-ai-advisors-vector-storemaven | >=1.0.0,<1.0.6 | 1.0.6 |
| org.springframework.ai:spring-ai-advisors-vector-storemaven | >=1.1.0,<1.1.5 | 1.1.5 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-40966 records a Medium severity secret exfiltration vulnerability in Spring AI's VectorStoreChatMemoryAdvisor conversation scoping can lead to cross-tenant memory exfiltration. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for org.springframework.ai:spring-ai-advisors-vector-store, org.springframework.ai:spring-ai-advisors-vector-store.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate org.springframework.ai:spring-ai-advisors-vector-store to 1.0.6; org.springframework.ai:spring-ai-advisors-vector-store to 1.1.5 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSecret Exfiltration describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-40966 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| org.springframework.ai:spring-ai-advisors-vector-storemaven | >=1.0.0,<1.0.6 | 1.0.6 |
| org.springframework.ai:spring-ai-advisors-vector-storemaven | >=1.1.0,<1.1.5 | 1.1.5 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-40966 records a Medium severity secret exfiltration vulnerability in Spring AI's VectorStoreChatMemoryAdvisor conversation scoping can lead to cross-tenant memory exfiltration. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for org.springframework.ai:spring-ai-advisors-vector-store, org.springframework.ai:spring-ai-advisors-vector-store.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardIn Spring AI, an attacker can bypass conversation isolation and exfiltrate sensitive memory from other users’ chat histories, including secrets and credentials, by injecting filter logic through conversationId. Only applications that use VectorStoreChatMemoryAdvisor and pass user-supplied input as a conversationId are affected.
In Spring AI, an attacker can bypass conversation isolation and exfiltrate sensitive memory from other users’ chat histories, including secrets and credentials, by injecting filter logic through conversationId. Only applications that use VectorStoreChatMemoryAdvisor and pass user-supplied input as a conversationId are affected.