Skip to content
feed: live
0dayNews
CVE Record
[ CRITICAL ]CVE-2022-22965

Spring4Shell — Spring Framework Remote Code Execution

A remote-code-execution vulnerability in the Spring Framework, stewarded by VMware, allows an attacker to achieve RCE via data binding under specific conditions — JDK 9+, Spring Framework versions before 5.3.18 / 5.2.20, and deployment as a traditional WAR on Apache Tomcat.

Vendor
VMware
Product
Spring Framework
CVSS
9.8
EPSS (exploit probability)
99.6%
Status
kev
CISA patch-by (BOD 22-01)
Published

Is CVE-2022-22965 being exploited?

Yes. CISA added CVE-2022-22965 to its Known Exploited Vulnerabilities catalog on . CISA only lists a CVE when it has reliable evidence of exploitation in the wild.

FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 99.6% (scored October 14, 2026).

Catalog snapshot 2026-11-17. Full cross-catalog view: /kev-comparison

CVE-2022-22965 timeline

  1. Published to NVD
  2. Added to CISA KEV+3d
  3. First 0dayNews coverage+1555d

Every event links to its source. Catalog dates are each catalog's own; day offsets count from NVD publication. Data: JSON

What to do

US federal civilian agencies must remediate by (21 days after listing) under BOD 22-01. Everyone else: that deadline is a sensible upper bound, not a target. Vendor guidance and the NVD record are linked under Source above.

CVE-2022-22965, quickly dubbed “Spring4Shell” for its proximity in name and disclosure timing to Log4Shell, is a remote-code-execution vulnerability in the Spring Framework, the widely used Java application framework stewarded by VMware. Disclosed March 31, 2022 after proof-of-concept exploit details leaked publicly ahead of an official patch, the flaw allows a remote attacker to manipulate the Spring data-binding process to reach the underlying ClassLoader and ultimately write a malicious file to a web-accessible path, achieving code execution — under a specific but not uncommon combination of conditions: JDK 9 or later, Spring MVC or Spring WebFlux, and deployment as a traditional WAR file on Apache Tomcat.

Why it mattered

Spring underpins a huge share of enterprise Java web applications, and the narrower (but still widespread) set of vulnerable deployment conditions meant security teams had to triage carefully rather than assume blanket exposure — a harder task than Log4Shell’s near-universal applicability, and one that led to real confusion in the first 48 hours about which applications were actually at risk. VMware shipped patches the same day details leaked, and CISA added the CVE to its KEV catalog shortly after confirmed in-the-wild exploitation.

Because the vulnerable conditions were specific, VMware’s advisory doubled as risk-triage guidance: organizations not running the exact vulnerable combination were not at risk from this specific CVE, though the framework-level patch was recommended regardless. Full technical detail and the complete list of vulnerable configurations are in VMware’s/Spring’s security advisory and at the NVD link above.

CVE / VulnerabilitySeverityCVSSEPSSAdded to KEV
CVE-2025-22226
VMware ESXi, Workstation, and Fusion Information Disclosure Vulnerability
[ HIGH ]7.11.6%
CVE-2025-22225
VMware ESXi Arbitrary Write Vulnerabilityransomware use
[ HIGH ]8.21.0%
CVE-2025-22224
VMware ESXi and Workstation TOCTOU Race Condition Vulnerability
[ CRITICAL ]9.31.6%
CVE-2024-38813
VMware vCenter Server Privilege Escalation Vulnerability
[ HIGH ]7.517.4%
CVE-2024-38812
VMware vCenter Server Heap-Based Buffer Overflow Vulnerability
[ CRITICAL ]9.854.6%
CVE-2024-37085
VMware ESXi Authentication Bypass Vulnerabilityransomware use
[ MEDIUM ]6.826.8%
CVE-2022-22948
VMware vCenter Server Incorrect Default File Permissions Vulnerability
[ MEDIUM ]6.513.3%
CVE-2023-34048
VMware vCenter Server Out-of-Bounds Write Vulnerability
[ CRITICAL ]9.899.2%
All 26 VMware CVEs →