Skip to main content
VulnerabilityPublished Updated

CVE-2026-41697: Spring Data Relational · Improper Neutralization of Special Elements in Data Query Logic

Affects Spring Data RelationalSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium · fixed in 4.0.5.1 : update Spring Data Relational when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.5.1, 3.5.11.1, 3.4.15 +6
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
SpringSpring Data RelationalAffected
  • >=4.0.0 <4.0.5.1
Fixed in
  • 4.0.5.1
SpringSpring Data RelationalAffected
  • >=3.5.0 <3.5.11.1
Fixed in
  • 3.5.11.1
SpringSpring Data RelationalAffected
  • >=3.4.0 <3.4.15
Fixed in
  • 3.4.15
SpringSpring Data RelationalAffected
  • >=3.3.0 <3.3.17
Fixed in
  • 3.3.17
SpringSpring Data RelationalAffected
  • >=3.2.0 <3.2.16
Fixed in
  • 3.2.16
SpringSpring Data RelationalAffected
  • >=3.1.0 <3.1.15
Fixed in
  • 3.1.15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…