CVE-2026-41719 — spring-data-keyvalue
MEDIUMCVE-2026-41719 is a medium-severity (CVSS 6.4) Expression Language Injection vulnerability in org.springframework.data:spring-data-keyvalue. A fix is available for org.springframework.data:spring-data-keyvalue — see the affected versions and patch details below.
Spring Data KeyValue - SpEL Injection vulnerability in SpelPropertyComparator
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41719.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-41719 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.data:spring-data-keyvalue☕org.springframework.data:spring-data-keyvalue☕org.springframework.data:spring-data-keyvalue☕org.springframework.data:spring-data-keyvalue☕org.springframework.data:spring-data-keyvalueReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.data:spring-data-keyvalue | ≥ 4.0.0&&< 4.0.6 | 4.0.6org.springframework.data:spring-data-keyvalue:4.0.6 |
| ☕Maven | org.springframework.data:spring-data-keyvalue | ≥ 3.5.0&&< 3.5.12 | 3.5.12org.springframework.data:spring-data-keyvalue:3.5.12 |
| ☕Maven | org.springframework.data:spring-data-keyvalue | ≥ 3.4.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-keyvalue | ≥ 3.0.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-keyvalue | all versions | No fix |
Affected Products
spring data keyvaluebroadcomspring data redisbroadcomDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-keyvalue, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.data:spring-data-keyvalue to 4.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41719 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
A flaw was found in Spring Data KeyValue. The SpelPropertyComparator used for sorting in KeyValue repository queries does not properly neutralize SpEL expressions, allowing an attacker to inject arbitrary expressions. Exploitation requires the application to use KeyValue repository queries with user-controlled Sort…
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2026-41719 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-41719 in your dependencies?
Find it across Maven, including transitive dependencies.