CVE-2026-41697 - Vulnerability Details

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

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.

Published: 2026-06-09

Score: 4.8 Medium

EPSS: < 1% Very Low

KEV: No

Impact:

Action:

Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

Spring

Spring Data Relational

unaffected

Version	Status	Constraints
`4.0.0`	affected	< 4.0.5.1
`3.5.0`	affected	< 3.5.11.1
`3.4.0`	affected	< 3.4.15
`3.3.0`	affected	< 3.3.17
`3.2.0`	affected	< 3.2.16
`3.1.0`	affected	< 3.1.15
`3.0.0`	affected	< 3.0.16
`2.4.0`	affected	< 2.4.20

Spring

Spring Data JDBC

unaffected

Version	Status	Constraints
`4.0.0`	affected	< 4.0.5.1
`3.5.0`	affected	< 3.5.11.1
`3.4.0`	affected	< 3.4.15
`3.3.0`	affected	< 3.3.17
`3.2.0`	affected	< 3.2.16
`3.1.0`	affected	< 3.1.15
`3.0.0`	affected	< 3.0.16
`2.4.0`	affected	< 2.4.20

Spring

Spring Data R2DBC

unaffected

Version	Status	Constraints
`4.0.0`	affected	< 4.0.5.1
`3.5.0`	affected	< 3.5.11.1
`3.4.0`	affected	< 3.4.15
`3.3.0`	affected	< 3.3.17
`3.2.0`	affected	< 3.2.16
`3.1.0`	affected	< 3.1.15
`3.0.0`	affected	< 3.0.16
`1.5.0`	affected	< 1.5.20

No data.

Vendor Product Confidence Versions

Spring

Spring Data Jdbc

100%

Version	Status	Scheme	Platform
`[4.0.0,4.0.6)`	affected	semver	—
`[3.5.0,3.5.12)`	affected	semver	—
`[3.4.0,3.4.15)`	affected	semver	—
`[3.3.0,3.3.17)`	affected	semver	—
`[3.2.0,3.2.16)`	affected	semver	—
`[3.1.0,3.1.15)`	affected	semver	—
`[3.0.0,3.0.16)`	affected	semver	—
`[2.4.0,2.4.20)`	affected	semver	—

Spring

Spring Data R2dbc

100%

Version	Status	Scheme	Platform
`[4.0.0,4.0.6)`	affected	semver	—
`[3.5.0,3.5.12)`	affected	semver	—
`[3.4.0,3.4.15)`	affected	semver	—
`[3.3.0,3.3.17)`	affected	semver	—
`[3.2.0,3.2.16)`	affected	semver	—
`[3.1.0,3.1.15)`	affected	semver	—
`[3.0.0,3.0.16)`	affected	semver	—
`[1.5.0,1.5.20)`	affected	semver	—

Spring

Spring Data Relational

100%

Version	Status	Scheme	Platform
`[4.0.0,4.0.6)`	affected	semver	—
`[3.5.0,3.5.12)`	affected	semver	—
`[3.4.0,3.4.15)`	affected	semver	—
`[3.3.0,3.3.17)`	affected	semver	—
`[3.2.0,3.2.16)`	affected	semver	—
`[3.1.0,3.1.15)`	affected	semver	—
`[3.0.0,3.0.16)`	affected	semver	—
`[2.4.0,2.4.20)`	affected	semver	—

Found an issue or want to improve our Enrichment? You can suggest it directly by opening an issue on our dedicated GitHub repository .

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

No CVSS v4.0

Attack Vector Network

Attack Complexity High

Privileges Required None

Scope Unchanged

Confidentiality Impact Low

Integrity Impact None

Availability Impact Low

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

The EPSS score is 0.00227.

Exploitation none

Automatable no

Technical Impact partial

References

Link	Providers
https://spring.io/security/cve-2026-41697

History

Wed, 10 Jun 2026 18:30:00 +0000

Type	Values Removed	Values Added
Metrics		ssvc `{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}`

Wed, 10 Jun 2026 11:30:00 +0000

Type	Values Removed	Values Added
First Time appeared		Spring Spring spring Data Jdbc Spring spring Data R2dbc Spring spring Data Relational
Vendors & Products		Spring Spring spring Data Jdbc Spring spring Data R2dbc Spring spring Data Relational

Wed, 10 Jun 2026 00:00:00 +0000

Type	Values Removed	Values Added
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.
Title		Spring Data Relational Parameter not Escaped for Query By Example LIKE Pattern
Weaknesses		CWE-943
References		https://spring.io/security/cve-2026-41697
Metrics		cvssV3_1 `{'score': 4.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L'}`

Subscriptions

Spring Spring Data Jdbc Spring Data R2dbc Spring Data Relational

MITRE

Status: PUBLISHED

Assigner: vmware

Published: 2026-06-09T23:47:42.091Z

Updated: 2026-06-27T21:33:25.580Z

Reserved: 2026-04-22T06:21:22.981Z

Link: CVE-2026-41697

Vulnrichment

Updated: 2026-06-10T17:51:21.717Z

NVD

Status : Awaiting Analysis

Published: 2026-06-10T00:16:50.947

Modified: 2026-06-10T19:24:04.320

Link: CVE-2026-41697

Redhat

No data.

OpenCVE Enrichment

Updated: 2026-06-10T11:21:48Z

Weaknesses

CWE-943

Tracking

Attack Vector Network

Attack Complexity High

Privileges Required None

Scope Unchanged

Confidentiality Impact Low

Integrity Impact None

Availability Impact Low

User Interaction None

Exploitation none

Automatable no

Technical Impact partial

Subscriptions

JSON object

JSON object

JSON object

JSON object

JSON object