CVE-2022-22965
CRITICALRemote Code Execution in Spring Framework
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
org.springframework:spring-beans☕org.springframework:spring-beans☕org.springframework:spring-webmvc☕org.springframework:spring-webmvc☕org.springframework.boot:spring-boot-starter-web☕org.springframework.boot:spring-boot-starter-web☕org.springframework:spring-webflux☕org.springframework:spring-webflux+2 moreReal-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
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. The specific exploit requires the application to run on Tomcat as a WAR deployment. If the application is deployed as a Spring Boot executable jar, i.e. the default, it is not vulnerable to the exploit. However, the nature of the vulnerability is more general, and there may be other ways to exploit it.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-beans | all versions | 5.2.20.RELEASE |
| ☕Maven | org.springframework:spring-beans | ≥ 5.3.0&&< 5.3.18 | 5.3.18 |
| ☕Maven | org.springframework:spring-webmvc | all versions | 5.2.20.RELEASE |
| ☕Maven | org.springframework:spring-webmvc | ≥ 5.3.0&&< 5.3.18 | 5.3.18 |
| ☕Maven | org.springframework.boot:spring-boot-starter-web | all versions | 2.5.12 |
| ☕Maven | org.springframework.boot:spring-boot-starter-web | ≥ 2.6.0&&< 2.6.6 | 2.6.6 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vuln…
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vuln…
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vuln…
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vuln…
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vuln…
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vuln…
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vuln…
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vuln…
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vuln…
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vuln…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-beans. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework:spring-beans to 5.2.20.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-22965 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-22965 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-22965. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-22965 in your dependencies?
O3 detects CVE-2022-22965 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.