CVE-2026-41713: VMware Spring AI · Template Injection
Affects VMware Spring AISource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 1.1.6 or 1.0.7 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% 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:L/I:H/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 15 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
|
Mavencom.vmware/spring-aipkg:maven/com.vmware/spring-aiOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restricting or sanitizing user-controlled input before it is stored in conversation memory may reduce risk, but this is not a vendor-provided mitigation.
Description
A malicious user could craft input that is stored in conversation memory and later interpreted by the model in an unintended way. Applications using the affected advisor with user-controlled input may be susceptible to manipulation of model behavior across conversation turns.