Spring AI: Improper Neutralization of Special Elements Used in a Template Engine
CVE-2026-41713 is a high-severity improper neutralization of special elements used in a template engine vulnerability in Spring AI from VMware, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 1.0.7, 1.1.6 as the first without the flaw, so updating Spring AI to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.22% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Spring AI to 1.0.7 or 1.1.6, whichever matches your release line, or a later version.
- Read the advisory on spring.io for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| VMware | Spring AI | 1.0.0 up to, but not including, 1.0.7; 1.1.0 up to, but not including, 1.1.6 | 1.0.7, 1.1.6 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N. Scored by CNA (vmware.com).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements Used in a Template Engine
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.
How developers prevent this class of flaw
- Choose a template engine that offers a sandbox or restricted mode, or at least limits the power of any available expressions, function calls, or commands.
- Use the template engine's sandbox or restricted mode, if available.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
Other vulnerabilities in Spring AI
- 7.5 High severity
- 8.8 High severity
- 8.6 High severity
Recent Improper Neutralization of Special Elements Used in a Template Engine vulnerabilities
- 8.3 High severity
- 8.8 High severity
- 8.1 High severity
- 7.8 High severity
- 7.2 High severity
- 9.9 Critical severity
Spotted an error? Tell us.