# CVE-2026-41719: Spring Data KeyValue - SpEL Injection vulnerability in SpelPropertyComparator > Attackers can execute arbitrary code via SpEL injection in Spring Data KeyValue when unsanitized user input is used in sort parameters. - **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Jun 2026 - **Updated:** 30 Jun 2026 - **Also known as:** CLEANSTART-2026-AO69724, CLEANSTART-2026-BI57203, CLEANSTART-2026-GV33004, CLSA-2026-1791467859, CLSA-2026-1791979377, CLSA-2026-1792421347, CLSA-2026-1792427749, CLSA-2026-1792490239, CLSA-2026-1792491026, CLSA-2026-1792657708, CLSA-2026-1792660304, CLSA-2026-1792661279, CLSA-2026-1792666371, CLSA-2026-1793184702, CLSA-2026-1793201948, GHSA-xg2j-3hj6-pc24, MINI-9g3r-mxmc-3c6h ## What is CVE-2026-41719? CVE-2026-41719 is a medium-severity code injection vulnerability in Spring Data KeyValue, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-917 (Improper Neutralization of Special Elements used in an Expression Language Statement) ## Which versions are affected by CVE-2026-41719? 10 open source packages ship an affected version, including org.springframework.data:spring-data-keyvalue. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.data:spring-data-keyvalue` | Maven | All versions to 2.7.19 | None | | `org.springframework.data:spring-data-keyvalue` | Maven | All versions to 2.7.19 | None | | `org.springframework.data:spring-data-keyvalue` | Maven | From 3.0.0 to 3.3.16 | None | | `org.springframework.data:spring-data-keyvalue` | Maven | From 3.0.0 to 3.3.16 | None | | `org.springframework.data:spring-data-keyvalue` | Maven | From 3.4.0 to 3.4.14 | None | | `org.springframework.data:spring-data-keyvalue` | Maven | From 3.4.0 to 3.4.14 | None | | `org.springframework.data:spring-data-keyvalue` | Maven | From 3.5.0 | 3.5.12 | | `org.springframework.data:spring-data-keyvalue` | Maven | From 3.5.0 | 3.5.12 | | `org.springframework.data:spring-data-keyvalue` | Maven | From 4.0.0 | 4.0.6 | | `org.springframework.data:spring-data-keyvalue` | Maven | From 4.0.0 | 4.0.6 | Products: Broadcom Spring Data Keyvalue, Broadcom Spring Data Redis. ## How do I fix CVE-2026-41719? Upgrade org.springframework.data:spring-data-keyvalue to a fixed version for your release line: 3.5.12 or 4.0.6. ## Is CVE-2026-41719 being exploited? There is no known exploitation of CVE-2026-41719 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-41719 and fix it if it is affected. What it is: CVE-2026-41719 is a medium-severity code injection vulnerability in Spring Data KeyValue, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-41719 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.data:spring-data-keyvalue (Maven): affected all versions up to 2.7.19; no fix listed - org.springframework.data:spring-data-keyvalue (Maven): affected all versions up to 2.7.19; no fix listed - org.springframework.data:spring-data-keyvalue (Maven): affected from 3.0.0 up to 3.3.16; no fix listed - org.springframework.data:spring-data-keyvalue (Maven): affected from 3.0.0 up to 3.3.16; no fix listed - org.springframework.data:spring-data-keyvalue (Maven): affected from 3.4.0 up to 3.4.14; no fix listed - org.springframework.data:spring-data-keyvalue (Maven): affected from 3.4.0 up to 3.4.14; no fix listed - org.springframework.data:spring-data-keyvalue (Maven): affected from 3.5.0; fixed in 3.5.12 - org.springframework.data:spring-data-keyvalue (Maven): affected from 3.5.0; fixed in 3.5.12 - org.springframework.data:spring-data-keyvalue (Maven): affected from 4.0.0; fixed in 4.0.6 - org.springframework.data:spring-data-keyvalue (Maven): affected from 4.0.0; fixed in 4.0.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-41719/ (Markdown: https://insights.sbomify.com/CVE-2026-41719/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41719 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41719 - OSV: https://osv.dev/vulnerability/CVE-2026-41719 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-41719/ Summaries are generated and may contain mistakes; the official description above is the record.