CVE-2026-41711
Received Received - Intake
Denial of Service in Spring Data Commons via Sort Parameter

Publication date: 2026-06-10

Last updated on: 2026-06-10

Assigner: VMware

Description
Applications using Spring Data Commons may be vulnerable to a Denial of Service (DoS) attack leading to a StackOverflowException when parsing Sort parameters. Affected versions: Spring Data Commons 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.7.0 through 2.7.19.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-10
Last Modified
2026-06-10
Generated
2026-06-10
AI Q&A
2026-06-10
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 8 associated CPEs
Vendor Product Version / Range
vmware spring_data_commons From 2.7.0 (inc) to 2.7.19 (inc)
vmware spring_data_commons From 3.0.0 (inc) to 3.0.15 (inc)
vmware spring_data_commons From 3.1.0 (inc) to 3.1.14 (inc)
vmware spring_data_commons From 3.2.0 (inc) to 3.2.15 (inc)
vmware spring_data_commons From 3.3.0 (inc) to 3.3.16 (inc)
vmware spring_data_commons From 3.4.0 (inc) to 3.4.14 (inc)
vmware spring_data_commons From 3.5.0 (inc) to 3.5.11 (inc)
vmware spring_data_commons From 4.0.0 (inc) to 4.0.5 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-41711 is a medium-severity vulnerability in applications using Spring Data Commons. It allows a Denial of Service (DoS) attack by causing a StackOverflowException when parsing specially crafted Sort parameters.

This happens if an application exposes endpoints that accept Sort parameters from untrusted sources without proper sanitization, or if endpoints use parameters annotated with @ProjectedPayload or @QuerydslPredicate.

Spring Data Commons itself does not expose this API to untrusted callers, so the risk depends on how the consuming Spring Data module or application code handles input.

Impact Analysis

This vulnerability can lead to a Denial of Service (DoS) condition in your application by causing it to throw a StackOverflowException when processing maliciously crafted Sort parameters.

If your application accepts Sort parameters from untrusted sources without proper input sanitization, an attacker could exploit this to crash or disrupt your service.

Detection Guidance

This vulnerability arises when applications using affected versions of Spring Data Commons parse crafted Sort parameters, potentially leading to a StackOverflowException. Detection involves identifying if your application exposes endpoints that accept Sort parameters from untrusted sources or uses parameters annotated with @ProjectedPayload or @QuerydslPredicate.

To detect exploitation attempts or the presence of this vulnerability, you can monitor application logs for StackOverflowException errors related to Sort parameter parsing.

  • Check application logs for StackOverflowException stack traces.
  • Use network monitoring tools to detect unusual or malformed requests targeting endpoints that accept Sort parameters.
  • If you have access to the application source or runtime, search for usage of Sort parameters or annotations like @ProjectedPayload or @QuerydslPredicate in your codebase.

Specific commands depend on your environment and logging setup, but examples include:

  • On Linux, to search logs for StackOverflowException: grep -i 'StackOverflowException' /path/to/application/logs/*
  • To monitor live logs for such exceptions: tail -f /path/to/application/logs/* | grep -i 'StackOverflowException'
  • Use network capture tools like tcpdump or Wireshark to analyze traffic for suspicious Sort parameter usage.
Mitigation Strategies

To mitigate this vulnerability, the primary step is to upgrade Spring Data Commons to a fixed version that addresses the issue.

  • Upgrade to version 4.0.6 if using 4.0.x series.
  • Upgrade to version 3.5.12 if using 3.5.x series.
  • Upgrade to version 3.4.15 if using 3.4.x series.
  • Upgrade to version 3.3.17 if using 3.3.x series.
  • Upgrade to version 2.7.20 if using 2.7.x series.

Note that some fixed versions are only available through Enterprise Support.

Additionally, ensure that any untrusted input intended for sorting is properly sanitized before processing to reduce the risk of exploitation.

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.

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