vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-41697

Spring Data Relational Parameter not Escaped for Query By Example LIKE Pattern

MEDIUM
4.8
CVSS Score
Published: June 9, 2026 at 11:47 PM UTC
Updated: September 4, 2026 at 07:36 PM UTC
4 products affected across 2 vendorsSpring Data RelationalSpring Data R2DBCSpring Data Relational

Using Spring Data Relational by Spring?

Get instant alerts when new vulnerabilities affect Spring Data Relational - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
MEDIUM4.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Spring Data Relational· Broadcom
95%
v < 2.4.203.0.0 ≤ v < 3.3.173.4.0 ≤ v < 3.4.153.5.0 ≤ v < 3.5.11.14.0.0 ≤ v < 4.0.5.1
Affected range stops below 2.4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.11.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.5.1, so it looks safe — our inference, not a vendor statement
Spring Data JDBC· Spring
60%
2.4.0 ≤ v < 2.4.203.0.0 ≤ v < 3.0.163.1.0 ≤ v < 3.1.153.2.0 ≤ v < 3.2.163.3.0 ≤ v < 3.3.173.4.0 ≤ v < 3.4.153.5.0 ≤ v < 3.5.11.14.0.0 ≤ v < 4.0.5.12.4.03.0.03.1.03.2.03.3.03.4.03.5.04.0.0
Affected range stops below 2.4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.11.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.5.1, so it looks safe — our inference, not a vendor statement
Spring Data R2DBC· Spring
60%
1.5.0 ≤ v < 1.5.203.0.0 ≤ v < 3.0.163.1.0 ≤ v < 3.1.153.2.0 ≤ v < 3.2.163.3.0 ≤ v < 3.3.173.4.0 ≤ v < 3.4.153.5.0 ≤ v < 3.5.11.14.0.0 ≤ v < 4.0.5.11.5.03.0.03.1.03.2.03.3.03.4.03.5.04.0.0
Affected range stops below 1.5.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.11.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.5.1, so it looks safe — our inference, not a vendor statement
Spring Data Relational· Spring
60%
2.4.0 ≤ v < 2.4.203.0.0 ≤ v < 3.0.163.1.0 ≤ v < 3.1.153.2.0 ≤ v < 3.2.163.3.0 ≤ v < 3.3.173.4.0 ≤ v < 3.4.153.5.0 ≤ v < 3.5.11.14.0.0 ≤ v < 4.0.5.12.4.03.0.03.1.03.2.03.3.03.4.03.5.04.0.0
Affected range stops below 2.4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.11.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.5.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor Advisory
Source: cverecord
https://spring.io/security/cve-2026-41697

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.8MEDIUMvmware
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-943

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card