Skip to main content
VulnerabilityPublished Updated

CVE-2026-41716: Spring Data Commons · Unthrottled Resource Allocation

Affects Spring Data CommonsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High · fixed in 4.0.5.1 : patch Spring Data Commons soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% 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 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 29 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
SpringSpring Data CommonsAffected
  • >=4.0.0 <4.0.5.1
Fixed in
  • 4.0.5.1
SpringSpring Data CommonsAffected
  • >=3.5.0 <3.5.11.1
Fixed in
  • 3.5.11.1
SpringSpring Data CommonsAffected
  • >=3.4.0 <3.4.15
Fixed in
  • 3.4.15
SpringSpring Data CommonsAffected
  • >=3.3.0 <3.3.17
Fixed in
  • 3.3.17
SpringSpring Data CommonsAffected
  • >=2.7.0 <2.7.20
Fixed in
  • 2.7.20

AI-suggested

If you cannot patch yet, consider implementing rate limiting or request throttling at the application or network level to reduce the risk of heap exhaustion from repeated requests with unique cache keys.

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.

References

Community reviews

Loading reviews…