CVE-2026-41697: Spring Data Relational Parameter not Escaped for Query By Example LIKE Pattern
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41697?
CVE-2026-41697 has a medium severity rating of 4.8.
What are the impacts of CVE-2026-41697?
CVE-2026-41697 can allow attackers to perform boolean-based blind data inference due to improper escaping of binding values.
How do I fix CVE-2026-41697?
To fix CVE-2026-41697, upgrade to the latest version of Spring Data Relational, Spring Data JDBC, or Spring Data R2DBC where the vulnerability has been addressed.
Which software is affected by CVE-2026-41697?
CVE-2026-41697 affects Spring Data Relational, Spring Data JDBC, and Spring Data R2DBC.
What type of input does CVE-2026-41697 target?
CVE-2026-41697 targets externally-controlled input supplied in Query By Example with specific StringMatcher patterns.