Is CVE-2026-41711 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41711 being exploited in the wild.

How severe is CVE-2026-41711?

Medium severity, with a CVSS score of 5.9, published 10 June 2026.

Which products and versions are affected?

org.springframework.data:spring-data-commons (Maven) ECOSYSTEM:introduced=4.0.0,fixed=4.0.6.

Is there a fix for CVE-2026-41711?

Yes. org.springframework.data:spring-data-commons (Maven): upgrade to 4.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41711 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-41711?

Check whether you run org.springframework.data:spring-data-commons (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41711: VMware Spring Data Commons DoS in Sort parameter parsing

CVE-2026-41711 · Severity: medium · CVSS 5.9 · Published 2026-06-10

Spring Data Commons is a widely used library for managing data access in Java applications. A vulnerability exists where processing specifically crafted sorting requests can cause the application to crash due to a memory error. This allows an attacker to disrupt the availability of the service, potentially leading to a complete system outage.

Technologies: org.springframework.data:spring-data-commons (Maven). Vendors: Maven.

Quick answers

Is CVE-2026-41711 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41711 being exploited in the wild.
How severe is CVE-2026-41711?: Medium severity, with a CVSS score of 5.9, published 10 June 2026.
Which products and versions are affected?: org.springframework.data:spring-data-commons (Maven) ECOSYSTEM:introduced=4.0.0,fixed=4.0.6.
Is there a fix for CVE-2026-41711?: Yes. org.springframework.data:spring-data-commons (Maven): upgrade to 4.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41711 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-41711?: Check whether you run org.springframework.data:spring-data-commons (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.springframework.data:spring-data-commons (Maven): upgrade to 4.0.6 or later

# set org.springframework.data:spring-data-commons to 4.0.6 in your pom.xml or build.gradle

Technical details

A Denial of Service (DoS) vulnerability exists in Spring Data Commons due to uncontrolled resource consumption (CWE-400) during the parsing of 'Sort' parameters. An attacker can provide specially crafted input that triggers a StackOverflowException, causing the Java Virtual Machine (JVM) thread to fail and potentially exhausting application resources. The attack is reachable over the network and requires no specific privileges, though it is rated with high attack complexity. Patches have been released in versions 4.0.6 and 3.5.12 to address this issue.

Affected products

Spring Spring Data Commons 4.0.0 to 4.0.5, 3.5.0 to 3.5.11, 3.4.0 to 3.4.14, 3.3.0 to 3.3.16, 3.2.0 to 3.2.15, 3.1.0 to 3.1.14, 3.0.0 to 3.0.15, 2.7.0 to 2.7.19

Identifiers

CVE-2026-41711
GHSA-5vpf-xvv7-c8vh

Timeline

2026-06-10: disclosed
2026-06-10: advisory
2026-06-09: patched: Versions 4.0.6 and 3.5.12 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.