CVE-2026-41717
VMware Spring Data Mongodb code injection
- Published9 Jun 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-41717 being actively exploited?
CVE-2026-41717 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.42%.
How severe is CVE-2026-41717?
CVE-2026-41717 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.42% probability of exploitation.
Which products are affected by CVE-2026-41717?
Affected products include VMware Spring Data Mongodb.
How do I fix CVE-2026-41717?
Upgrade affected software to a fixed version, for example VMware Spring Data Mongodb 3.4.20 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-41717 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.