Spring Data REST: Improper Neutralization of Special Elements used in an Expression Language Statement
CVE-2026-41729 is a high-severity improper neutralization of special elements used in an expression language statement vulnerability in Spring Data REST from Spring, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 3.7.20, 4.3.17, 4.4.15 as the first without the flaw, so updating Spring Data REST to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.41% 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 Data REST to 3.7.20 or 4.3.17 or 4.4.15 or 4.5.12, whichever matches your release line, or a later version.
- Read the advisory on spring.io for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Spring | Spring Data REST | 3.7.0 up to, but not including, 3.7.20; 4.3.0 up to, but not including, 4.3.17; 4.4.0 up to, but not including, 4.4.15; 4.5.0 up to, but not including, 4.5.12; 5.0.0 up to, but not including, 5.0.6 | 3.7.20, 4.3.17, 4.4.15, 4.5.12, 5.0.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
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component 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:L/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (vmware.com).
Official description
Spring Data REST is vulnerable to SpEL expression injection through map-typed properties when processing JSON Patch (application/json-patch+json) requests. When a persistent entity exposes a Map-typed property, the JSON Pointer path segment used as the map key is embedded directly into a SpEL expression without sanitization or validation. Affected versions: Spring Data REST 3.7.0 through 3.7.19; 4.3.0 through 4.3.16; 4.4.0 through 4.4.14; 4.5.0 through 4.5.11; 5.0.0 through 5.0.5.
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 an Expression Language Statement
The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.
How developers prevent this class of flaw
- Avoid adding user-controlled data into an expression interpreter when possible.
- If user-controlled data must be added to an expression interpreter, one or more of the following should be performed: Validate that the user input will not evaluate as an expression Encode the user input in a way that ensures it is not evaluated as an expression
- The framework or tooling might allow the developer to disable or deactivate the processing of EL expressions, such as setting the isELIgnored attribute for a JSP page to true.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Spring Data REST
- 7.1 High severity
- 7.5 High severity
Recent Improper Neutralization of Special Elements used in an Expression Language Statement vulnerabilities
- 8.1 High severity
- 7.5 High severity
- 9.6 Critical severity
- 9.0 Critical severity
- 8.6 High severity
- 8.1 High severity
Spotted an error? Tell us.