Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

SpEL Expression Injection in Spring Data MongoDB Annotated Query Parameter Binding

IdentifiersCVE-2026-41717CWE-917· Improper Neutralization of Special…

CVE-2026-41717 is a Spring Expression Language (SpEL) expression injection vulnerability in Spring Data MongoDB. The flaw occurs during parameter binding when a user-defined repository method uses annotated queries with a capture-all placeholder, including cases described with @Query and, per the provided content, also @Aggregation. Example vulnerable patterns include capture-all placeholders such as @Query("?0") and @Query(":#{?0}"). If untrusted, unsanitized input is passed directly into such repository methods, attacker-controlled input can be interpreted in an unsafe expression context during query construction. Affected versions are 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, and 3.4.0 through 3.4.19.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow attacker-controlled SpEL expression injection during query parameter binding. Based on the provided content and CVSS vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, impact can be severe, including unauthorized query manipulation and potentially arbitrary code execution on the underlying host in vulnerable application deployments, with high impact to confidentiality, integrity, and availability.

Mitigation

If you can’t patch tonight, do this now.

Avoid exposing affected repository methods to untrusted input until patched. Specifically, do not pass unsanitized user-controlled data directly into repository methods annotated with capture-all placeholders in @Query or @Aggregation. Review repository definitions for patterns such as @Query("?0") and @Query(":#{?0}") and refactor to safer query construction that does not evaluate attacker-controlled expressions. Where exposure exists through spring-data-rest or custom web endpoints, restrict or sanitize input paths and reduce external reachability until upgrades are completed.

Remediation

Patch, then assume compromise.

Upgrade Spring Data MongoDB to a fixed release on the relevant branch. The provided content identifies fixed versions as 5.0.6 for 5.0.x, 4.5.12 for 4.5.x, 4.4.15 for 4.4.x, 4.3.17 for 4.3.x, and 3.4.20 for 3.4.x. The content further states that fixes for 5.0.x and 4.5.x are available through OSS releases, while fixes for 4.4.x, 4.3.x, and 3.4.x are available through Enterprise Support. Users should move to the corresponding fixed version or a later supported release.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
BroadcomSpring Data Mongodbapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.