CVE-2026-41697 json
Spring Data Relational Parameter not Escaped for Query By Example LIKE Pattern
published 2026-06-09 5 mo ago modified 2026-09-04 2 mo ago also GHSA-8r2h-xh92-gq57 , EUVD-2026-35893
- cvss
- 4.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.springframework.data:spring-data-relational 3.5.12, 4.0.6
- Spring Spring Data Relational 2.4.20, 3.0.16, 3.1.15, 3.2.16, 3.3.17, 3.4.15, 3.5.11.1, 4.0.5.1
- Spring Spring Data JDBC 2.4.20, 3.0.16, 3.1.15, 3.2.16, 3.3.17, 3.4.15, 3.5.11.1, 4.0.5.1
- Spring Spring Data R2DBC 1.5.20, 3.0.16, 3.1.15, 3.2.16, 3.3.17, 3.4.15, 3.5.11.1, 4.0.5.1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-41697 updated cvss 3.7
Spring Data Relational: Spring Data Relational: Information disclosure via improper input escaping in Query By Example
-
Red Hat JBoss Enterprise Application Platform Expansion Pack spring-data-relationalaffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L |
| GitHub | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.data:spring-data-relational | >=4.0.0, <4.0.6 >=3.5.0, <3.5.12 >=3.4.0, <=3.4.14 >=3.0.0, <=3.3.16 <=2.4.19 |
4.0.6 3.5.12 |
Affected products
- Spring Spring Data Relational
- Spring Spring Data JDBC
- Spring Spring Data R2DBC
Classification
- Weakness
-
- CWE-943 Improper Neutralization of Special Elements in Data Query Logic
References
-
spring.io
/security/cve-2026-41697
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-41697
advisory
-
github.com
/spring-projects/spring-data-relational
package
-
github.com
/spring-projects/spring-data-relational/releases/tag/3.5.12
web
-
github.com
/spring-projects/spring-data-relational/releases/tag/4.0.6
web
Sources
- CVE List CVE-2026-41697
- GitHub Advisory GHSA-8r2h-xh92-gq57
- NVD CVE-2026-41697
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.