Skip to content
Fencer Intel
medium 5.9

CVE-2026-40966 json

VectorStoreChatMemoryAdvisor conversation scoping can lead to cross-tenant memory exfiltration

published 6mo ago modified 14d ago also GHSA-v6x6-pjxw-3pv2 , EUVD-2026-26002

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.springframework.ai:spring-ai-advisors-vector-store 1.0.6, 1.1.5
  • VMware Spring AI 1.0.6, 1.1.5

Is CVE-2026-40966 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
6mo ago

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.ai:spring-ai-advisors-vector-store
>=1.0.0, <1.0.6
>=1.1.0, <1.1.5
1.0.6
1.1.5

Affected products

  • VMware Spring AI

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.