CVE-2026-41717
SpEL injection in Spring Data MongoDB query binding.
Is CVE-2026-41717 being exploited?
Not confirmed. CVE-2026-41717 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-41717?
CVE-2026-41717 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41717?
Yes. A fix has been recorded for CVE-2026-41717. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41717 affect?
CVE-2026-41717 affects Spring Data MongoDB 3.4.x–5.0.x. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41717?
Upgrade to the patched Spring Data MongoDB release.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted SpEL in @Query parameters during binding (capture-all).
Patch when possible
- affected>= 5.0.0 and < 5.0.5.1
- affected>= 4.5.0 and < 4.5.11.1
- affected>= 4.4.0 and < 4.4.15
- affected>= 4.3.0 and < 4.3.17
- affected>= 4.2.0 and < 4.2.16
- affected>= 4.1.0 and < 4.1.15
- affected>= 4.0.0 and < 4.0.16
- affected>= 3.4.0 and < 3.4.20
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.