CyberSecBulletin
CVE-2026-41717NVD status: Analyzed

Spring Data MongoDB: Improper Neutralization of Special Elements used in an Expression Language Statement

Published Updated By the CyberSecBulletin desk

CVE-2026-41717 is a high-severity improper neutralization of special elements used in an expression language statement vulnerability in Spring Data MongoDB from Spring, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 5.0.5.1, 4.5.11.1, 4.4.15 as the first without the flaw, so updating Spring Data MongoDB to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.33% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Spring Data MongoDB to 5.0.5.1 or 4.5.11.1 or 4.4.15 or 4.3.17, whichever matches your release line, or a later version.
  2. Read the advisory on spring.io for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
SpringSpring Data MongoDB5.0.0 up to, but not including, 5.0.5.1; 4.5.0 up to, but not including, 4.5.11.1; 4.4.0 up to, but not including, 4.4.15; 4.3.0 up to, but not including, 4.3.17; 4.2.0 up to, but not including, 4.2.16; 4.1.0 up to, but not including, 4.1.15; 4.0.0 up to, but not including, 4.0.16; 3.4.0 up to, but not including, 3.4.205.0.5.1, 4.5.11.1, 4.4.15, 4.3.17, 4.2.16, 4.1.15

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (vmware.com).

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Neutralization of Special Elements used in an Expression Language Statement

The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.

How developers prevent this class of flaw

  • Avoid adding user-controlled data into an expression interpreter when possible.
  • If user-controlled data must be added to an expression interpreter, one or more of the following should be performed: Validate that the user input will not evaluate as an expression Encode the user input in a way that ensures it is not evaluated as an expression
  • The framework or tooling might allow the developer to disable or deactivate the processing of EL expressions, such as setting the isELIgnored attribute for a JSP page to true.

More Improper Neutralization of Special Elements used in an Expression Language Statement vulnerabilities (CWE-917)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Neutralization of Special Elements used in an Expression Language Statement vulnerabilities

Spotted an error? Tell us.