CVE-2026-41716
HIGHCVE-2026-41716 is a high-severity (CVSS 7.5) CWE-770 vulnerability in org.springframework.data:spring-data-commons. O3 Security confirms whether CVE-2026-41716 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Spring Data web support unbounded negative-result cache keyed on attacker-supplied property names
Real-World Exposure
org.springframework.data:spring-data-commons☕org.springframework.data:spring-data-commons☕org.springframework.data:spring-data-commons☕org.springframework.data:spring-data-commons☕org.springframework.data:spring-data-commonsReal-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's internal property-lookup cache accepts and permanently retains attacker-supplied strings as cache keys, allowing heap exhaustion through repeated requests.
Affected versions: Spring Data Commons 2.7.0 through 2.7.19; 3.3.0 through 3.3.16; 3.4.0 through 3.4.14; 3.5.0 through 3.5.11; 4.0.0 through 4.0.5.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.data:spring-data-commons | ≥ 4.0.0&&< 4.0.6 | 4.0.6 |
| ☕Maven | org.springframework.data:spring-data-commons | ≥ 3.5.0&&< 3.5.12 | 3.5.12 |
| ☕Maven | org.springframework.data:spring-data-commons | ≥ 3.4.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-commons | ≥ 3.3.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-commons | 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-commons. 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-commons to 4.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41716 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-41716 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-41716. 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-41716 in your dependencies?
O3 detects CVE-2026-41716 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.