CVE-2026-41696 is a medium-severity (CVSS 5.9) CWE-943 vulnerability in org.springframework.data:spring-data-mongodb. A fix is available for org.springframework.data:spring-data-mongodb — see the affected versions and patch details below.
Spring Data MongoDB Bind Parameter Literal Quoting Breakout
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41696.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-41696 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 380,066 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.data:spring-data-mongodb☕org.springframework.data:spring-data-mongodb☕org.springframework.data:spring-data-mongodb☕org.springframework.data:spring-data-mongodb☕org.springframework.data:spring-data-mongodbReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Spring 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.data:spring-data-mongodb | ≥ 5.0.0&&< 5.0.6 | 5.0.6org.springframework.data:spring-data-mongodb:5.0.6 |
| ☕Maven | org.springframework.data:spring-data-mongodb | ≥ 4.5.0&&< 4.5.12 | 4.5.12org.springframework.data:spring-data-mongodb:4.5.12 |
| ☕Maven | org.springframework.data:spring-data-mongodb | ≥ 4.4.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-mongodb | ≥ 4.0.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-mongodb | all versions | No fix |
Affected Products
spring data mongodbvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-mongodb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.data:spring-data-mongodb to 5.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41696 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2026-41696 in your dependencies?
Find it across Maven, including transitive dependencies.