CVE-2026-41697: CWE-943: Improper Neutralization of Special Elements in Data Query Logic in Spring Spring Data Relational
Spring Data Relational does not properly escape binding values of externally-controlled input when using StringMatcher (STARTING, ENDING, or CONTAINING) in Query By Example (QBE). An attacker can supply wildcard characters to perform boolean-based blind data inference. Affected versions: Spring Data Relational/JDBC/R2DBC 4.0.0 through 4.0.5; 3.5.0 through 3.5.11; 3.4.0 through 3.4.14; 3.3.0 through 3.3.16; 3.2.0 through 3.2.15; 3.1.0 through 3.1.14; 3.0.0 through 3.0.15; 2.4.0 through 2.4.19.
AI Analysis
Technical Summary
CVE-2026-41697 affects Spring Data Relational and related modules (JDBC, R2DBC) in versions 2.4.0 through 4.0.5. The issue arises because the software does not properly escape binding values of externally-controlled input when using StringMatcher options (STARTING, ENDING, or CONTAINING) in Query By Example (QBE). This improper neutralization of special elements in data query logic can be exploited by an attacker who supplies wildcard characters, enabling boolean-based blind data inference attacks. The vulnerability is identified as CWE-943.
Potential Impact
An attacker can leverage this vulnerability to perform boolean-based blind data inference by injecting wildcard characters into query inputs. This may lead to unauthorized inference of sensitive data. The CVSS vector indicates network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, low confidentiality impact, no integrity impact, and low availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary mitigation has been published at this time. Users should monitor vendor communications for updates and consider restricting or validating input to Query By Example StringMatcher parameters as a precaution.
CVE-2026-41697: CWE-943: Improper Neutralization of Special Elements in Data Query Logic in Spring Spring Data Relational
Description
Spring Data Relational does not properly escape binding values of externally-controlled input when using StringMatcher (STARTING, ENDING, or CONTAINING) in Query By Example (QBE). An attacker can supply wildcard characters to perform boolean-based blind data inference. Affected versions: Spring Data Relational/JDBC/R2DBC 4.0.0 through 4.0.5; 3.5.0 through 3.5.11; 3.4.0 through 3.4.14; 3.3.0 through 3.3.16; 3.2.0 through 3.2.15; 3.1.0 through 3.1.14; 3.0.0 through 3.0.15; 2.4.0 through 2.4.19.
CVSS v3.1
Score 4.8medium
Affected software
pkg:maven/org.springframework.data/spring-data-relationalRun 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-41697 affects Spring Data Relational and related modules (JDBC, R2DBC) in versions 2.4.0 through 4.0.5. The issue arises because the software does not properly escape binding values of externally-controlled input when using StringMatcher options (STARTING, ENDING, or CONTAINING) in Query By Example (QBE). This improper neutralization of special elements in data query logic can be exploited by an attacker who supplies wildcard characters, enabling boolean-based blind data inference attacks. The vulnerability is identified as CWE-943.
Potential Impact
An attacker can leverage this vulnerability to perform boolean-based blind data inference by injecting wildcard characters into query inputs. This may lead to unauthorized inference of sensitive data. The CVSS vector indicates network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, low confidentiality impact, no integrity impact, and low availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary mitigation has been published at this time. Users should monitor vendor communications for updates and consider restricting or validating input to Query By Example StringMatcher parameters as a precaution.
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: 6a28a8028dd33fbd8595ef6d
Added to database: 06/09/2026, 23:55:46 UTC
Last enriched: 06/28/2026, 21:00:14 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 65
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.