CVE-2026-41697
MEDIUMCVE-2026-41697 is a medium-severity (CVSS 4.8) CWE-943 vulnerability in org.springframework.data:spring-data-relational. O3 Security confirms whether CVE-2026-41697 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Spring Data Relational: Attackers can supply wildcard characters to perform boolean-based blind data inference
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.
Real-World Exposure
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-relationalReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.data:spring-data-relational | ≥ 4.0.0&&< 4.0.6 | 4.0.6 |
| ☕Maven | org.springframework.data:spring-data-relational | ≥ 3.5.0&&< 3.5.12 | 3.5.12 |
| ☕Maven | org.springframework.data:spring-data-relational | ≥ 3.4.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-relational | ≥ 3.0.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-relational | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-relational. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
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.
How O3 protects you
O3 pinpoints whether CVE-2026-41697 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-41697. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-41697 in your dependencies?
O3 detects CVE-2026-41697 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.