CVE-2026-41717 — spring-data-mongodb
HIGHCVE-2026-41717 is a high-severity (CVSS 8.1) Expression Language Injection vulnerability in org.springframework.data:spring-data-mongodb. A fix is available for org.springframework.data:spring-data-mongodb — see the affected versions and patch details below.
Spring Data MongoDB - SpEL Expression Injection via Annotated Query Parameter Binding
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-41717.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-41717 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 380,526 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-mongodb☕org.springframework.data:spring-data-mongodb☕org.springframework.data:spring-data-mongodb☕org.springframework.data:spring-data-mongodb☕org.springframework.data:spring-data-mongodbReal-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
Spring Data MongoDB contains a SpEL (Spring Expression Language) expression injection vulnerability. The issue occurs during parameter binding when a user-defined repository query method is annotated with @Query and utilizes a capture-all placeholder.
Affected versions: Spring Data MongoDB 5.0.0 through 5.0.5; 4.5.0 through 4.5.11; 4.4.0 through 4.4.14; 4.3.0 through 4.3.16; 4.2.0 through 4.2.15; 4.1.0 through 4.1.14; 4.0.0 through 4.0.15; 3.4.0 through 3.4.19.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.data:spring-data-mongodb | ≥ 5.0.0&&< 5.0.6 | 5.0.6org.springframework.data:spring-data-mongodb:5.0.6 |
| ☕Maven | org.springframework.data:spring-data-mongodb | ≥ 4.5.0&&< 4.5.12 | 4.5.12org.springframework.data:spring-data-mongodb:4.5.12 |
| ☕Maven | org.springframework.data:spring-data-mongodb | ≥ 4.4.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-mongodb | ≥ 4.0.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-mongodb | all versions | No fix |
Affected Products
spring data mongodbvmwareDetection & 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-mongodb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.data:spring-data-mongodb to 5.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41717 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.
The vulnerability in Spring Data MongoDB is rated as Important. However, Red Hat products, including Red Hat JBoss Fuse, are not affected by this flaw as the vulnerable code is not present in these offerings.
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-41717 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-41717 in your dependencies?
Find it across Maven, including transitive dependencies.