CVE-2021-22044 — spring-cloud-openfeign-co…
HIGHCVE-2021-22044 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.springframework.cloud:spring-cloud-openfeign-core. A fix is available for org.springframework.cloud:spring-cloud-openfeign-core — see the affected versions and patch details below.
Exposure of Resource to Wrong Sphere in Spring Cloud OpenFeign
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.cloud:spring-cloud-openfeign-core☕org.springframework.cloud:spring-cloud-openfeign-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 Cloud OpenFeign 3.0.0 to 3.0.4, 2.2.0.RELEASE to 2.2.9.RELEASE, and older unsupported versions, applications using type-level @RequestMappingannotations over Feign client interfaces, can be involuntarily exposing endpoints corresponding to @RequestMapping-annotated interface methods.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.cloud:spring-cloud-openfeign-core | ≥ 3.0.0&&< 3.0.5 | 3.0.5org.springframework.cloud:spring-cloud-openfeign-core:3.0.5 |
| ☕Maven | org.springframework.cloud:spring-cloud-openfeign-core | ≥ 2.2.0&&< 2.2.10 | 2.2.10org.springframework.cloud:spring-cloud-openfeign-core:2.2.10 |
Affected Products
spring cloud openfeignvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-openfeign-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.cloud:spring-cloud-openfeign-core to 3.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-22044 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 CVE-2021-22044 in your dependencies?
Find it across Maven, including transitive dependencies.