GHSA-cv39-x4c6-hhp2 — spring-data-rest-core
HIGHGHSA-cv39-x4c6-hhp2 is a high-severity (CVSS 7.5) CWE-284 vulnerability in org.springframework.data:spring-data-rest-core. A fix is available for org.springframework.data:spring-data-rest-core — see the affected versions and patch details below.
Spring Data REST has Improper Access Control in its JSON Patch Implementation
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-cv39-x4c6-hhp2.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-cv39-x4c6-hhp2 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.data:spring-data-rest-core☕org.springframework.data:spring-data-rest-core☕org.springframework.data:spring-data-rest-core☕org.springframework.data:spring-data-rest-core☕org.springframework.data:spring-data-rest-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.data:spring-data-rest-core | ≥ 5.0.0&&< 5.0.6 | 5.0.6org.springframework.data:spring-data-rest-core:5.0.6 |
| ☕Maven | org.springframework.data:spring-data-rest-core | ≥ 4.5.0&&< 4.5.12 | 4.5.12org.springframework.data:spring-data-rest-core:4.5.12 |
| ☕Maven | org.springframework.data:spring-data-rest-core | ≥ 4.4.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-rest-core | ≥ 4.3.0 | No fix |
| ☕Maven | org.springframework.data:spring-data-rest-core | all versions | No fix |
Affected Products
spring data restvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-rest-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.data:spring-data-rest-core to 5.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cv39-x4c6-hhp2 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-cv39-x4c6-hhp2 in your dependencies?
Find it across Maven, including transitive dependencies.