CVE-2026-41696: CWE-943: Improper Neutralization of Special Elements in Data Query Logic in Spring Spring Data MongoDB
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.
AI Analysis
Technical Summary
CVE-2026-41696 affects Spring Data MongoDB repository query methods annotated with @Query that use regex parameter binding. The vulnerability arises from insufficient validation of the bound regex parameter, which can be manipulated by an attacker to break out of the intended regular expression quoting. This improper neutralization of special elements in data query logic may lead to unintended query behavior. The CVSS v3.1 base score is 5.9 (medium severity), with network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact. No official patch or remediation level has been published yet, and no known exploits are reported in the wild.
Potential Impact
An attacker can craft a malicious string parameter to bypass the intended regex quoting in Spring Data MongoDB queries, potentially causing unauthorized data exposure due to improper query filtering. The confidentiality impact is rated high, but there is no impact on integrity or availability. Exploitation requires network access and is of high complexity, with no privileges or user interaction needed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should avoid using regex parameter binding in @Query methods or implement strict input validation and sanitization on regex parameters to prevent injection of special characters that could break regex quoting.
CVE-2026-41696: CWE-943: Improper Neutralization of Special Elements in Data Query Logic in Spring Spring Data MongoDB
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.
CVSS v3.1
Score 5.9medium
Affected software
pkg:maven/org.springframework.data/spring-data-mongodbRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-41696 affects Spring Data MongoDB repository query methods annotated with @Query that use regex parameter binding. The vulnerability arises from insufficient validation of the bound regex parameter, which can be manipulated by an attacker to break out of the intended regular expression quoting. This improper neutralization of special elements in data query logic may lead to unintended query behavior. The CVSS v3.1 base score is 5.9 (medium severity), with network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact. No official patch or remediation level has been published yet, and no known exploits are reported in the wild.
Potential Impact
An attacker can craft a malicious string parameter to bypass the intended regex quoting in Spring Data MongoDB queries, potentially causing unauthorized data exposure due to improper query filtering. The confidentiality impact is rated high, but there is no impact on integrity or availability. Exploitation requires network access and is of high complexity, with no privileges or user interaction needed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should avoid using regex parameter binding in @Query methods or implement strict input validation and sanitization on regex parameters to prevent injection of special characters that could break regex quoting.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-04-22T06:21:22.981Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a28a8028dd33fbd8595ef6a
Added to database: 06/09/2026, 23:55:46 UTC
Last enriched: 06/17/2026, 08:49:23 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 85
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.