# CVE-2026-41711: Potential Denial of Service through crafted Sort Parameters > Attackers can cause a denial of service via crafted sort parameters in Spring Data Commons, requiring an upgrade to patched versions. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Jun 2026 - **Updated:** 27 Jun 2026 - **Also known as:** CLEANSTART-2026-PG68728, CLEANSTART-2026-UH14817, CLEANSTART-2026-YB42445, CLSA-2026-1789999868, CLSA-2026-1790687278, CLSA-2026-1790691700, GHSA-5vpf-xvv7-c8vh, MINI-mphj-9c6h-2c48, MINI-vchq-qrxv-8r9m, MINI-w73j-pr2f-9h2r ## What is CVE-2026-41711? CVE-2026-41711 is a medium-severity denial of service vulnerability in Spring Data Commons, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2026-41711? 10 open source packages ship an affected version, including org.springframework.data:spring-data-commons. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.data:spring-data-commons` | Maven | All versions to 2.7.19 | None | | `org.springframework.data:spring-data-commons` | Maven | All versions to 2.7.19 | None | | `org.springframework.data:spring-data-commons` | Maven | From 3.0.0 to 3.3.16 | None | | `org.springframework.data:spring-data-commons` | Maven | From 3.0.0 to 3.3.16 | None | | `org.springframework.data:spring-data-commons` | Maven | From 3.4.0 to 3.4.14 | None | | `org.springframework.data:spring-data-commons` | Maven | From 3.4.0 to 3.4.14 | None | | `org.springframework.data:spring-data-commons` | Maven | From 3.5.0 | 3.5.12 | | `org.springframework.data:spring-data-commons` | Maven | From 3.5.0 | 3.5.12 | | `org.springframework.data:spring-data-commons` | Maven | From 4.0.0 | 4.0.6 | | `org.springframework.data:spring-data-commons` | Maven | From 4.0.0 | 4.0.6 | Products: Broadcom Spring Data Commons. ## How do I fix CVE-2026-41711? Upgrade org.springframework.data:spring-data-commons to a fixed version for your release line: 3.5.12 or 4.0.6. ## Is CVE-2026-41711 being exploited? There is no known exploitation of CVE-2026-41711 in the wild and no public exploit code. ## Other vulnerabilities in Spring Data Commons - [CVE-2026-41695](https://insights.sbomify.com/CVE-2026-41695/): Denial of Service in Spring Data Commons Property Path Resolution (high 7.5) - [CVE-2026-41716](https://insights.sbomify.com/CVE-2026-41716/): Spring Data web support unbounded negative-result cache keyed on attacker-supplied property names (high 7.5) - [CVE-2018-1259](https://insights.sbomify.com/CVE-2018-1259/): Spring Data Commons, used in combination with XMLBeam, contains a property binder vulnerability caused by improper restriction of XML external entity references (high 7.5) - [CVE-2018-1274](https://insights.sbomify.com/CVE-2018-1274/): Spring Data Commons contain a property path parser vulnerability caused by unlimited resource allocation (high 7.5) - [CVE-2026-41721](https://insights.sbomify.com/CVE-2026-41721/): Spring Data Commons Denial of Service via Data Binding (medium 5.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-41711 and fix it if it is affected. What it is: CVE-2026-41711 is a medium-severity denial of service vulnerability in Spring Data Commons, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-41711 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.data:spring-data-commons (Maven): affected all versions up to 2.7.19; no fix listed - org.springframework.data:spring-data-commons (Maven): affected all versions up to 2.7.19; no fix listed - org.springframework.data:spring-data-commons (Maven): affected from 3.0.0 up to 3.3.16; no fix listed - org.springframework.data:spring-data-commons (Maven): affected from 3.0.0 up to 3.3.16; no fix listed - org.springframework.data:spring-data-commons (Maven): affected from 3.4.0 up to 3.4.14; no fix listed - org.springframework.data:spring-data-commons (Maven): affected from 3.4.0 up to 3.4.14; no fix listed - org.springframework.data:spring-data-commons (Maven): affected from 3.5.0; fixed in 3.5.12 - org.springframework.data:spring-data-commons (Maven): affected from 3.5.0; fixed in 3.5.12 - org.springframework.data:spring-data-commons (Maven): affected from 4.0.0; fixed in 4.0.6 - org.springframework.data:spring-data-commons (Maven): affected from 4.0.0; fixed in 4.0.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-41711/ (Markdown: https://insights.sbomify.com/CVE-2026-41711/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41711 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41711 - OSV: https://osv.dev/vulnerability/CVE-2026-41711 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-41711/ Summaries are generated and may contain mistakes; the official description above is the record.