Spring Data MongodbDatabase / datastore · VMware
CVE-2026-41696
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 repository query methods annotated with @Query that use regex parameter binding perform insufficient validation of the bound parameter. An attacker can supply a crafted string to break out of the intended regular expression quoting. 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 · moderate confidenceSpring Data MongoDB's @Query annotation with regex parameter binding fails to properly validate or escape input strings, allowing attackers to inject crafted regex patterns that can break out of intended quoting. This regex injection could cause denial of service via maliciously crafted regular expressions or potentially expose unexpected data through manipulated query behavior.
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.15>= 4.1.0, <= 4.1.14>= 4.2.0, <= 4.2.15>= 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the installed Spring Data MongoDB versionCheck your project's dependency management file (Maven pom.xml, Gradle build.gradle, or equivalent) for the spring-data-mongodb version. Alternatively, run 'mvn dependency:tree' or 'gradle dependencies' and locate the spring-data-mongodb artifact.Affected if The version falls within any of these ranges: >= 3.4.0 and < 3.4.20; >= 4.0.0 and <= 4.0.15; >= 4.1.0 and <= 4.1.14; >= 4.2.0 and <= 4.2.15; >= 4.3.0 and < 4.3.17; >= 4.4.0 and < 4.4.15; >= 4.5.0 and < 4.5.11.1; >= 5.0.0 and < 5.0.5.1
-
Locate @Query annotations using regex parameter bindingSearch your codebase for @Query annotations, particularly looking for parameters annotated with @Param that are used within the query string with regex operators ($regex) or where the parameter type is Pattern. Check MongoRepository interface definitions for @Query usage.Affected if The application uses @Query annotations where parameters are bound to regex patterns without sanitization
-
Verify if input validation exists on regex-bound parametersReview the code handling parameters passed to @Query methods. Check if there is validation logic that strips or escapes regex metacharacters (such as . * + ? ^ $ { } [ ] \ | ( ) ) before the parameter is used in the query.Affected if No input validation or sanitization is performed on parameters bound to regex patterns in @Query annotations
Your environment is affected if you use a vulnerable Spring Data MongoDB version AND your application uses @Query annotations with regex-bound parameters without input validation on those parameters.
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.3.174.4.15
Upgrade to patched versions of Spring Data MongoDB (noted in official advisories) and/or implement strict input validation/sanitization on all parameters bound to regex queries to prevent injection of regex metacharacters.
Spring Data MongoDB 3.4.20, 4.0.16, 4.1.15, 4.2.16, 4.3.17, 4.4.15, 4.5.12, or 5.0.6 (depending on your current major version line)
- 1. Identify the current Spring Data MongoDB version in your project's pom.xml or build.gradle file
- 2. Determine which major version line you are using (3.4.x, 4.0.x, 4.1.x, 4.2.x, 4.3.x, 4.4.x, 4.5.x, or 5.0.x)
- 3. For Spring Data MongoDB 3.4.x: upgrade to version 3.4.20 or later
- 4. For Spring Data MongoDB 4.0.x: upgrade to version 4.0.16 or later
- 5. For Spring Data MongoDB 4.1.x: upgrade to version 4.1.15 or later
- 6. For Spring Data MongoDB 4.2.x: upgrade to version 4.2.16 or later
- 7. For Spring Data MongoDB 4.3.x: upgrade to version 4.3.17 or later
- 8. For Spring Data MongoDB 4.4.x: upgrade to version 4.4.15 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
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41696 — 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-41696 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