CVE-2022-22965
KEVSpring Framework JDK 9+ Remote Code Execution Vulnerability
Description
Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding.
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.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HPublishedApr 1, 2022
Last modifiedJun 17, 2026
Added to KEVApr 4, 2022
Remediation dueApr 25, 2022
References
- packetstormsecurity.com/files/166713/Spring4Shell-Code-Execution.htmlExploitThird Party Advisory
- packetstormsecurity.com/files/167011/Spring4Shell-Spring-Framework-Class-Property-Remote-Code-Execution.htmlThird Party AdvisoryVDB Entry
- cert-portal.siemens.com/productcert/pdf/ssa-254054.pdfPatchThird Party Advisory
- psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0005Third Party Advisory
- tanzu.vmware.com/security/cve-2022-22965MitigationVendor Advisory
- tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-java-spring-rce-Zx9GUc67Third Party Advisory
- oracle.com/security-alerts/cpuapr2022.htmlThird Party Advisory
- oracle.com/security-alerts/cpujul2022.htmlPatchThird Party Advisory
- kb.cert.org/vuls/id/970766US Government Resource
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-22965US Government Resource
0 recent articles mention this CVE
89
Risk assessment · Critical
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1645 days
- CVSS
- 9.8 CRITICAL
- EPSS (30-day exploit probability)
- 99.6% · top 1% of all CVEs
- Weakness
- CWE-94
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
Recommended actions
- 1.Apply updates per vendor instructions.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.