CVE-2026-41719
Spring Data KeyValue - SpEL Injection vulnerability in SpelPropertyComparator
MEDIUM
6.4
CVSS Score
Published: June 9, 2026 at 11:48 PM UTC
Updated: July 23, 2026 at 07:32 PM UTC
4 products affected across 2 vendorsSpring Data RedisSpring Data KeyvalueSpring Data Redis
Using Spring Data KeyValue by Spring?
Get instant alerts when new vulnerabilities affect Spring Data KeyValue - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.4
Exploit prediction
EPSS 0.2%
SSVC
No known exploit
Description
A SpEL Injection vulnerability exists in the Spring Data KeyValue if unsanitized user input is passed as Sort into a repository query method that delegates evaluation to the SpelPropertyComparator. Affected versions: Spring Data KeyValue / Spring Data Redis 4.0.0 through 4.0.5; 3.5.0 through 3.5.11; 3.4.0 through 3.4.14; 3.3.0 through 3.3.16; 3.2.0 through 3.2.15; 3.1.0 through 3.1.14; 3.0.0 through 3.0.15; 2.7.0 through 2.7.19.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
2.7.0 ≤ v < 2.7.203.0.0 ≤ v < 3.0.163.1.0 ≤ v < 3.1.153.2.0 ≤ v < 3.2.163.3.0 ≤ v < 3.3.173.4.0 ≤ v < 3.4.153.5.0 ≤ v < 3.5.11.14.0.0 ≤ v < 4.0.5.1
Affected range stops below 2.7.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.11.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.5.1, so it looks safe — our inference, not a vendor statement
2.7.0 ≤ v < 2.7.203.0.0 ≤ v < 3.0.163.1.0 ≤ v < 3.1.153.2.0 ≤ v < 3.2.163.3.0 ≤ v < 3.3.173.4.0 ≤ v < 3.4.153.5.0 ≤ v < 3.5.11.14.0.0 ≤ v < 4.0.5.1
Affected range stops below 2.7.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.11.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.5.1, so it looks safe — our inference, not a vendor statement
2.7.0 ≤ v < 2.7.203.0.0 ≤ v < 3.0.163.1.0 ≤ v < 3.1.153.2.0 ≤ v < 3.2.163.3.0 ≤ v < 3.3.173.4.0 ≤ v < 3.4.153.5.0 ≤ v < 3.5.11.14.0.0 ≤ v < 4.0.5.12.7.03.0.03.1.03.2.03.3.03.4.03.5.04.0.0
Affected range stops below 2.7.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.11.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.5.1, so it looks safe — our inference, not a vendor statement
2.7.0 ≤ v < 2.7.203.0.0 ≤ v < 3.0.163.1.0 ≤ v < 3.1.153.2.0 ≤ v < 3.2.163.3.0 ≤ v < 3.3.173.4.0 ≤ v < 3.4.153.5.0 ≤ v < 3.5.11.14.0.0 ≤ v < 4.0.5.12.7.03.0.03.1.03.2.03.3.03.4.03.5.04.0.0
Affected range stops below 2.7.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.11.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.5.1, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
References (1)
SSVC — Action Prioritization
SSVCNo known exploitNot automatablePartial impact
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
CVSS
6.4MEDIUMvmware
- Attack Vector
- NETWORK
- Complexity
- HIGH
- Privileges
- LOW
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- HIGH
- Integrity
- LOW
- Availability
- LOW
Vector?
Quick Info
StatusANALYZED
CWE
CWE-917
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card