Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
CISA KEV·Added 2022-04-04 — agencies required to remediate by 2022-04-25
Maven

CVE-2022-22965

CRITICAL

Remote Code Execution in Spring Framework

Also known asGHSA-36p3-wjmg-h94x
Published
Apr 1, 2022
Updated
Jul 15, 2026
Affected
10 pkgs
Patched
10 / 10
Exploits
106 known

EPSS Exploitation Probability

via FIRST.org ↗
99.7%probability of exploitation in next 30 days
Very High Risk100th percentile0.00%
92.9%95.2%97.6%100.0%94.4%99.7%Jan 26May 26Jul 26

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

10 pkgs affected
org.springframework:spring-beansorg.springframework:spring-beansorg.springframework:spring-webmvcorg.springframework:spring-webmvcorg.springframework.boot:spring-boot-starter-weborg.springframework.boot:spring-boot-starter-weborg.springframework:spring-webfluxorg.springframework:spring-webflux+2 more

Real-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

10 total 10 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.springframework:spring-beansall versions5.2.20.RELEASE
Mavenorg.springframework:spring-beans5.3.0&&< 5.3.185.3.18
Mavenorg.springframework:spring-webmvcall versions5.2.20.RELEASE
Mavenorg.springframework:spring-webmvc5.3.0&&< 5.3.185.3.18
Mavenorg.springframework.boot:spring-boot-starter-weball versions2.5.12
Mavenorg.springframework.boot:spring-boot-starter-web2.6.0&&< 2.6.62.6.6
Exploits & PoCs
106

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. 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.

  3. 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.

  4. 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

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.
O3 Security · Impact-Aware SCA

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.