Denial of Service in Spring Data Commons via Sort Parameter

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.

Useful 0 Not Useful 0

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.

Useful 0 Not Useful 0

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.

Useful 0 Not Useful 0

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.

Useful 0 Not Useful 0

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.

Useful 0 Not Useful 0