Spring Data MongodbDatabase / datastore · VMware
CVE-2026-41717
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSpring 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSpring Data MongoDB has a SpEL injection vulnerability in parameter binding for @Query annotated repository methods. When using capture-all placeholders (like ?0, ?1 for positional parameters), user input is evaluated as SpEL expressions instead of being treated as literal values, allowing an attacker to inject malicious SpEL that could execute arbitrary code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Spring Data MongodbDatabase / datastore
>= 3.4.0, < 3.4.20>= 4.0.0, < 4.0.16>= 4.1.0, < 4.1.15>= 4.2.0, < 4.2.16>= 4.3.0, < 4.3.17>= 4.4.0, < 4.4.15>= 4.5.0, <= 4.5.11.1>= 5.0.0, < 5.0.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Spring Data MongoDB versionCheck the pom.xml, build.gradle, or the spring-data-mongodb jar manifest for the version. In a running application, inspect the org.springframework.data.mongodb version from classpath or runtime dependencies.Affected if The installed version falls within >= 3.4.0 <= 3.4.19; >= 4.0.0 <= 4.0.15; >= 4.1.0 <= 4.1.14; >= 4.2.0 <= 4.2.15; >= 4.3.0 <= 4.3.16; >= 4.4.0 <= 4.4.11; >= 4.5.0 <= 4.5.11; >= 5.0.0 <= 5.0.5
-
Locate repository interfaces with @Query annotationsSearch source code for interfaces extending MongoRepository, ReactiveMongoRepository, or CrudRepository that contain @Query annotations. The pattern is @Query annotation with a MongoDB query string containing ?0, ?1, etc. placeholders or :paramName named parameters.Affected if Repository methods use @Query with parameter placeholders that accept user input
-
Inspect capture-all placeholder usage in @QueryExamine each @Query annotation for capture-all placeholders: ?0, ?1, ?2 (positional) or :parameterName (named) where the value comes from user-controllable method arguments. Capture-all placeholders bind the entire parameter value into the query expression.Affected if @Query annotations use positional (?0, ?1) or named (:param) placeholders that bind user input directly into the query without validation
-
Verify parameter exposureReview the repository method signatures to confirm parameters come from user-facing endpoints (REST controllers, services, or external inputs). Check if @Query parameters accept unauthenticated or externally supplied values.Affected if Repository method parameters accepting @RequestBody, @RequestParam, or other user-supplied values are passed to @Query methods with capture-all placeholders
You are affected if your application uses a vulnerable Spring Data MongoDB version AND has @Query annotated repository methods with capture-all placeholders (?0, ?1, :param) that accept user-controlled input without validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.4.204.0.164.1.15
Upgrade Spring Data MongoDB to a patched version. As a defensive measure, review and refactor @Query methods to avoid capture-all placeholders and use named parameters instead.
Upgrade to Spring Data MongoDB 3.4.20, 4.0.16, 4.1.15, 4.2.16, or a later version (4.3.17+, 4.4.15+, 4.5.12+, 5.0.6+) depending on your current major version
- Identify the current Spring Data MongoDB version in your project's dependency management (e.g., pom.xml, build.gradle)
- For Spring Data MongoDB 3.4.x: upgrade to version 3.4.20
- For Spring Data MongoDB 4.0.x: upgrade to version 4.0.16
- For Spring Data MongoDB 4.1.x: upgrade to version 4.1.15
- For Spring Data MongoDB 4.2.x: upgrade to version 4.2.16
- For Spring Data MongoDB 4.3.x: upgrade to version 4.3.17 or later
- For Spring Data MongoDB 4.4.x: upgrade to version 4.4.15 or later
- For Spring Data MongoDB 4.5.x: upgrade to version 4.5.12 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Data Mongodb
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41717 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41717 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data