CVE-2026-41716
Analyzed Analyzed - Analysis Complete

Heap Exhaustion in Spring Data Commons via Cache Key Injection

Vulnerability report for CVE-2026-41716, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-10

Last updated on: 2026-06-16

Assigner: VMware

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-10
Last Modified
2026-06-16
Generated
2026-06-30
AI Q&A
2026-06-10
EPSS Evaluated
2026-06-29
NVD
EUVD

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
broadcom spring_data_commons From 2.7.0 (inc) to 2.7.20 (exc)
broadcom spring_data_commons From 3.3.0 (inc) to 3.3.17 (exc)
broadcom spring_data_commons From 3.4.0 (inc) to 3.4.15 (exc)
broadcom spring_data_commons From 3.5.0 (inc) to 3.5.12 (exc)
broadcom spring_data_commons From 4.0.0 (inc) to 4.0.6 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Compliance Impact

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Executive Summary

CVE-2026-41716 is a vulnerability in Spring Data's internal property-lookup cache that allows an attacker to cause a denial of service by exhausting the heap memory.

The issue arises because the cache accepts and permanently stores attacker-supplied strings as cache keys without filtering, especially when HTTP-supplied strings are passed directly to PropertyPath.from.

This vulnerability is particularly relevant in applications using Querydsl web bindings with default permit-all visibility or @ProjectedPayload form-parameter binding via MapDataBinder.

Impact Analysis

This vulnerability can lead to a denial of service (DoS) condition by causing heap exhaustion.

Repeated requests with attacker-supplied strings cause the internal cache to grow indefinitely, consuming system memory and potentially crashing or severely degrading the affected application.

The impact is on system availability, making the service unavailable to legitimate users.

Mitigation Strategies

To mitigate the vulnerability CVE-2026-41716, you should upgrade your Spring Data Commons to one of the fixed versions depending on your current version.

  • Upgrade to version 2.7.20 if you are using any version from 2.7.0 through 2.7.19.
  • Upgrade to version 3.3.17 if you are using any version from 3.3.0 through 3.3.16.
  • Upgrade to version 3.4.15 if you are using any version from 3.4.0 through 3.4.14.
  • Upgrade to version 3.5.12 if you are using any version from 3.5.0 through 3.5.11.
  • Upgrade to version 4.0.6 if you are using any version from 4.0.0 through 4.0.5.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-41716. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart