# CVE-2026-41728: Spring Data REST JSON Patch bypasses Jackson read-only property protection on nested objects and collections > Attackers can modify protected nested object properties via JSON Patch requests, bypassing Jackson read-only restrictions in Spring Data REST applications. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **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:** 30 Jun 2026 - **Also known as:** CLSA-2026-1790958488, GHSA-cv39-x4c6-hhp2, ROOT-APP-MAVEN-CVE-2026-41728 ## What is CVE-2026-41728? CVE-2026-41728 is a high-severity missing authorization vulnerability in Spring Data REST, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Spring Data REST's JSON Patch (application/json-patch+json) implementation does not apply the write-access filter to intermediate path segments when resolving a multi-segment JSON Pointer. Affected versions: Spring Data REST 3.7.0 through 3.7.19; 4.3.0 through 4.3.16; 4.4.0 through 4.4.14; 4.5.0 through 4.5.11; 5.0.0 through 5.0.5. Weakness: CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2026-41728? 10 open source packages ship an affected version, including org.springframework.data:spring-data-rest-core. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.data:spring-data-rest-core` | Maven | All versions to 3.7.19 | None | | `org.springframework.data:spring-data-rest-core` | Maven | All versions to 3.7.19 | None | | `org.springframework.data:spring-data-rest-core` | Maven | From 4.3.0 to 4.3.16 | None | | `org.springframework.data:spring-data-rest-core` | Maven | From 4.3.0 to 4.3.16 | None | | `org.springframework.data:spring-data-rest-core` | Maven | From 4.4.0 to 4.4.14 | None | | `org.springframework.data:spring-data-rest-core` | Maven | From 4.4.0 to 4.4.14 | None | | `org.springframework.data:spring-data-rest-core` | Maven | From 4.5.0 | 4.5.12 | | `org.springframework.data:spring-data-rest-core` | Maven | From 4.5.0 | 4.5.12 | | `org.springframework.data:spring-data-rest-core` | Maven | From 5.0.0 | 5.0.6 | | `org.springframework.data:spring-data-rest-core` | Maven | From 5.0.0 | 5.0.6 | Products: Vmware Spring Data Rest. ## How do I fix CVE-2026-41728? Upgrade org.springframework.data:spring-data-rest-core to a fixed version for your release line: 4.5.12 or 5.0.6. ## Is CVE-2026-41728 being exploited? There is no known exploitation of CVE-2026-41728 in the wild and no public exploit code. ## Other vulnerabilities in Spring Data REST - [CVE-2026-41729](https://insights.sbomify.com/CVE-2026-41729/): Spring Data REST SpEL Injection via Map Key in JSON Patch (high 8.1) - [CVE-2026-47849](https://insights.sbomify.com/CVE-2026-47849/): Spring Data REST allows mutation of identifier and version properties via JSON Patch (high 7.1) - [CVE-2026-41730](https://insights.sbomify.com/CVE-2026-41730/): Spring Data REST exposes persistence-layer internals in error responses (medium 5.3) - [CVE-2026-41837](https://insights.sbomify.com/CVE-2026-41837/): Spring Data REST Querydsl integration exposes Jackson-hidden persistent fields as filter keys (medium 5.3) - [CVE-2021-22047](https://insights.sbomify.com/CVE-2021-22047/): Exposure of Resource to Wrong Sphere in Spring Data REST (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-41728 and fix it if it is affected. What it is: CVE-2026-41728 is a high-severity missing authorization vulnerability in Spring Data REST, 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-41728 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.data:spring-data-rest-core (Maven): affected all versions up to 3.7.19; no fix listed - org.springframework.data:spring-data-rest-core (Maven): affected all versions up to 3.7.19; no fix listed - org.springframework.data:spring-data-rest-core (Maven): affected from 4.3.0 up to 4.3.16; no fix listed - org.springframework.data:spring-data-rest-core (Maven): affected from 4.3.0 up to 4.3.16; no fix listed - org.springframework.data:spring-data-rest-core (Maven): affected from 4.4.0 up to 4.4.14; no fix listed - org.springframework.data:spring-data-rest-core (Maven): affected from 4.4.0 up to 4.4.14; no fix listed - org.springframework.data:spring-data-rest-core (Maven): affected from 4.5.0; fixed in 4.5.12 - org.springframework.data:spring-data-rest-core (Maven): affected from 4.5.0; fixed in 4.5.12 - org.springframework.data:spring-data-rest-core (Maven): affected from 5.0.0; fixed in 5.0.6 - org.springframework.data:spring-data-rest-core (Maven): affected from 5.0.0; fixed in 5.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-41728/ (Markdown: https://insights.sbomify.com/CVE-2026-41728/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41728 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41728 - OSV: https://osv.dev/vulnerability/CVE-2026-41728 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-41728/ Summaries are generated and may contain mistakes; the official description above is the record.