Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2026-41697 — spring-data-relational

MEDIUM

CVE-2026-41697 is a medium-severity (CVSS 4.8) CWE-943 vulnerability in org.springframework.data:spring-data-relational. A fix is available for org.springframework.data:spring-data-relational — see the affected versions and patch details below.

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

Also known asGHSA-8r2h-xh92-gq57
Published
Jun 9, 2026
Updated
Sep 12, 2026
Affected
5 pkgs
Patched
2 / 5
Exploits
None indexed
Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41697.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs20th percentile — riskier than 20% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-41697 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

5 pkgs affected
☕org.springframework.data:spring-data-relational☕org.springframework.data:spring-data-relational☕org.springframework.data:spring-data-relational☕org.springframework.data:spring-data-relational☕org.springframework.data:spring-data-relational

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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 Packages

5 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.springframework.data:spring-data-relational≥ 4.0.0&&< 4.0.64.0.6org.springframework.data:spring-data-relational:4.0.6
☕Mavenorg.springframework.data:spring-data-relational≥ 3.5.0&&< 3.5.123.5.12org.springframework.data:spring-data-relational:3.5.12
☕Mavenorg.springframework.data:spring-data-relational≥ 3.4.0No fix
☕Mavenorg.springframework.data:spring-data-relational≥ 3.0.0No fix
☕Mavenorg.springframework.data:spring-data-relationalall versionsNo fix

Affected Products

1 product · 5 configurations
Application
spring data relationalbroadcom
≥ 4.0.0 && < 4.0.5.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-relational, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.springframework.data:spring-data-relational to 4.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41697 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

A flaw was found in Spring Data Relational. The Query By Example implementation does not properly escape wildcard characters in StringMatcher bindings, allowing an attacker to perform boolean-based blind data inference. Exploitation requires the application to use QBE with StringMatcher (STARTING, ENDING, or…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2026-41697 (CC BY 4.0)

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-41697 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-41697: spring-data (Medium 4.8) | O3 Security