CVE-2026-41712: VMware Spring AI · Information Exposure
Affects VMware Spring AISource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 1.1.6 or 1.0.7 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.1.6, 1.0.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade VMware Spring AI to 1.1.6 or 1.0.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| VMwareSpring AI | Affected
| Fixed in
|
| VMwareSpring AI | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, users should review and explicitly override the default chat memory settings to prevent unintended data exposure.
Description
Spring AI's chat memory component contained a problematic default that, when not explicitly overridden, could result in unintended data exposure between users.