Exposure of Resource to Wrong Sphere in Spring Data RESTGHSA-4926-qpxg-6r3w
MEDIUMGHSA-4926-qpxg-6r3w is a medium-severity (CVSS 5.3) Information Exposure 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.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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
In Spring Data REST versions 3.4.0 - 3.4.13, 3.5.0 - 3.5.5, and older unsupported versions, HTTP resources implemented by custom controllers using a configured base API path and a controller type-level request mapping are additionally exposed under URIs that can potentially be exposed for unauthorized access depending on the Spring Security configuration.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.data:spring-data-rest-core | ≥ 3.4.0&&< 3.4.14 | 3.4.14org.springframework.data:spring-data-rest-core:3.4.14 |
| ☕Maven | org.springframework.data:spring-data-rest-core | ≥ 3.5.0&&< 3.5.6 | 3.5.6org.springframework.data:spring-data-rest-core:3.5.6 |
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 3.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4926-qpxg-6r3w is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-4926-qpxg-6r3w in your dependencies?
Find it across Maven, including transitive dependencies.