CVE-2026-41711
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApplications 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSpring Data Commons fails to properly handle specially crafted Sort parameters during parsing, leading to excessive recursion and ultimately a StackOverflowException that crashes the application. An attacker can exploit this by sending malicious Sort parameter values in HTTP requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.7.0, < 2.7.20>= 3.0.0, <= 3.0.15>= 3.1.0, <= 3.1.14>= 3.2.0, <= 3.2.15>= 3.3.0, < 3.3.17>= 3.4.0, < 3.4.15>= 3.5.0, < 3.5.11.1>= 4.0.0, < 4.0.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Spring Data Commons versionInspect your project's build file (Maven pom.xml or Gradle build.gradle) for the spring-data-commons dependency and note its version, or run 'mvn dependency:tree' or 'gradle dependencies' to list the resolved version.Affected if The installed version falls within any of these ranges: >= 2.7.0 and < 2.7.20; >= 3.0.0 and <= 3.0.15; >= 3.1.0 and <= 3.1.14; >= 3.2.0 and <= 3.2.15; >= 3.3.0 and < 3.3.17; >= 3.4.0 and < 3.4.15; >= 3.5.0 and < 3.5.11.1; >= 4.0.0 and < 4.0.5.1.
-
Confirm Spring Data repository usageSearch your codebase for interfaces extending Repository, CrudRepository, PagingAndSortingRepository, or JpaRepository from the org.springframework.data.repository package. Also check for usage of Sort in method signatures or the Sort parameter type.Affected if Your application uses Spring Data repositories with Sort parameters, which enables the vulnerable code path.
-
Check for exposed Sort-enabled endpointsReview your REST controllers or Spring Data REST repositories for endpoints that accept sort query parameters (for example, ?sort=field or nested sort like ?sort=field.subfield). Look for @RequestParam Sort or usage of Pageable parameters that include sorting.Affected if Your application exposes HTTP endpoints that accept sort parameters from clients without validation limits.
-
Verify input validation on Sort parametersSearch your application for any custom input validation, limits, or sanitization applied to Sort input before it reaches the repository layer. Check for validation libraries, custom interceptors, or middleware that restricts sort field depth or complexity.Affected if No input validation or depth limits are implemented on Sort parameter parsing, meaning deeply nested or recursive sort input can reach the vulnerable code.
You are affected if your application uses a vulnerable Spring Data Commons version AND exposes Sort-enabled API endpoints without validation, as malicious or deeply nested Sort input could trigger a StackOverflowException.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.7.203.3.173.4.15
Upgrade Spring Data Commons to the patched version (not yet specified in the advisory). If immediate patching is not possible, implement request size limits and validation on Sort parameters at the API gateway or web application firewall layer.
Spring Data Commons 2.7.20+, 3.0.16+, 3.1.15+, 3.2.16+, 3.3.17+, 3.4.15+, 3.5.12+, or 4.0.6+ depending on your version line
- 1. Identify the exact version of Spring Data Commons in your project by checking your build configuration (Maven pom.xml or Gradle build.gradle)
- 2. Determine which version line (2.7.x, 3.0.x, 3.1.x, 3.2.x, 3.3.x, 3.4.x, 3.5.x, or 4.0.x) your current version belongs to
- 3. For 2.7.x line: upgrade to version 2.7.20 or later
- 4. For 3.0.x line: upgrade to version 3.0.16 or later
- 5. For 3.1.x line: upgrade to version 3.1.15 or later
- 6. For 3.2.x line: upgrade to version 3.2.16 or later
- 7. For 3.3.x line: upgrade to version 3.3.17 or later
- 8. For 3.4.x line: upgrade to version 3.4.15 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41711 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41711 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data