CVE-2026-41716GHSA-9FW2-H3HF-293R
Spring Data web support unbounded negative-result cache keyed on attacker-supplied property names
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.7.20, 3.3.17, 3.4.15, 3.5.11.1, 4.0.5.1, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Spring Spring Data Commons
From 2.7.0 · fixed in 2.7.20; From 3.3.0 · fixed in 3.3.17; From 3.4.0 · fixed in 3.4.15; From 3.5.0 · fixed in 3.5.11.1; From 4.0.0 · fixed in 4.0.5.1
- org.springframework.data:spring-data-commonsMaven
From 4.0.0 · fixed in 4.0.6
- org.springframework.data:spring-data-commonsMaven
From 3.5.0 · fixed in 3.5.12
- org.springframework.data:spring-data-commonsMaven
From 3.4.0 · through 3.4.14
- org.springframework.data:spring-data-commonsMaven
From 3.3.0 · through 3.3.16
- org.springframework.data:spring-data-commonsMaven
through 2.7.19