Vmware Spring AI up to 1.0.6/1.1.5 Conversation Memory special elements in template engine
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Vmware Spring AI up to 1.0.6/1.1.5. Impacted is an unknown function of the component Conversation Memory Handler. The manipulation leads to special elements in template engine. This vulnerability is referenced as CVE-2026-41713. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Vmware Spring AI up to 1.0.6/1.1.5. It has been rated as critical. This issue affects some unknown processing of the component Conversation Memory Handler. The manipulation with an unknown input leads to a special elements in template engine vulnerability. Using CWE to declare the problem leads to CWE-1336. The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was published by Ahmed Sekka. The advisory is shared at spring.io. The identification of this vulnerability is CVE-2026-41713 since 04/22/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/12/2026). MITRE ATT&CK project uses the attack technique T1221 for this issue.
Upgrading to version 1.0.7 or 1.1.6 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.vmware.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.2
CNA Vector (vmware): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Special elements in template engineCWE: CWE-1336 / CWE-791 / CWE-790
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Spring AI 1.0.7/1.1.6
Timeline
04/22/2026 CVE reserved05/12/2026 Advisory disclosed
05/12/2026 VulDB entry created
05/12/2026 VulDB entry last update
Sources
Vendor: vmware.comAdvisory: spring.io
Researcher: Ahmed Sekka
Status: Confirmed
CVE: CVE-2026-41713 (🔒)
GCVE (CVE): GCVE-0-2026-41713
GCVE (VulDB): GCVE-100-363005
scip Labs: https://www.scip.ch/en/?labs.20060413
Entry
Created: 05/12/2026 13:40Changes: 05/12/2026 13:40 (65)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.