CVE-2022-22965

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-04-04), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
9.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 100%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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 v3
9.8
EG Score
9.8(high)
EPSS
99.9%
KEV
⚠ Exploited

Published

April 1, 2022

Last Modified

October 30, 2025

Advisory Details (5)

Auto-updated Jun 1, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

Packet Storm

http://packetstormsecurity.com/files/167011/Spring4Shell-Spring-Framework-Class-Property-Remote-Code-Execution.html
generic

Packet Storm

http://packetstormsecurity.com/files/166713/Spring4Shell-Code-Execution.html
generic🟡 PoC Available

Vulnerability in Spring Framework Affecting Cisco Products: March 2022

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-java-spring-rce-Zx9GUc67
generic

CVE-2022-22965: Spring Framework RCE via Data Binding on JDK 9+

https://tanzu.vmware.com/security/cve-2022-22965
generic

Security Advisory

https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0005

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibspring-web-servlet-java (4.3.30-2ubuntu0.24.10.1) @ oracular2026-07-11ubuntu
redhatspring-webmvc2022-04-27redhat
redhatpatch2022-04-27redhat
redhatspring-beans2022-04-12redhat
redhatpatch2022-04-11redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 1 ecosystem)
Maven(5)
PackageVulnerable rangeFixed inDependents
org.springframework.boot:spring-boot-starter-web2.6.0 ... 2.6.5 (6 versions)2.6.6—
org.springframework.boot:spring-boot-starter-webflux2.6.0 ... 2.6.5 (6 versions)2.6.6—
org.springframework:spring-beans5.3.0 ... 5.3.9 (18 versions)5.3.18—
org.springframework:spring-webflux5.3.0 ... 5.3.9 (18 versions)5.3.18—
org.springframework:spring-webmvc5.3.0 ... 5.3.9 (18 versions)5.3.18—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 0× in last 7d / 0× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 22:28 UTCEG score recompute
  2. 2026-07-11 22:28 UTCVendor advisory
  3. 2026-07-11 18:50 UTCEG score recompute
  4. 2026-07-11 18:50 UTCVendor advisory
  5. 2026-07-11 15:11 UTCEG score recompute
  6. 2026-07-11 15:11 UTCVendor advisory
  7. 2026-07-11 11:32 UTCEG score recompute
  8. 2026-07-11 11:32 UTCVendor advisory
  9. 2026-07-11 07:52 UTCEG score recompute
  10. 2026-07-11 07:52 UTCVendor advisory
  11. 2026-07-11 04:14 UTCEG score recompute
  12. 2026-07-11 04:14 UTCVendor advisory
  13. 2026-07-11 00:35 UTCEG score recompute
  14. 2026-07-11 00:35 UTCVendor advisory
  15. 2026-07-10 20:57 UTCEG score recompute
  16. 2026-07-10 20:57 UTCVendor advisory
  17. 2026-07-10 17:52 UTCCISA KEV update
  18. 2026-07-10 17:18 UTCEG score recompute
  19. 2026-07-10 17:18 UTCVendor advisory
  20. 2026-07-10 13:40 UTCEG score recompute
  21. 2026-07-10 13:40 UTCVendor advisory
  22. 2026-07-10 09:59 UTCEG score recompute
  23. 2026-07-10 09:59 UTCVendor advisory
  24. 2026-07-10 06:20 UTCEG score recompute
  25. 2026-07-10 06:20 UTCVendor advisory
Show 75 more
  1. 2026-07-10 02:42 UTCEG score recompute
  2. 2026-07-10 02:42 UTCVendor advisory
  3. 2026-07-09 23:03 UTCEG score recompute
  4. 2026-07-09 23:03 UTCVendor advisory
  5. 2026-07-09 19:24 UTCEG score recompute
  6. 2026-07-09 19:24 UTCVendor advisory
  7. 2026-07-09 15:45 UTCEG score recompute
  8. 2026-07-09 15:45 UTCVendor advisory
  9. 2026-07-09 12:06 UTCEG score recompute
  10. 2026-07-09 12:06 UTCVendor advisory
  11. 2026-07-09 08:28 UTCEG score recompute
  12. 2026-07-09 08:28 UTCVendor advisory
  13. 2026-07-09 04:48 UTCEG score recompute
  14. 2026-07-09 04:48 UTCVendor advisory
  15. 2026-07-09 01:10 UTCEG score recompute
  16. 2026-07-09 01:10 UTCVendor advisory
  17. 2026-07-08 21:31 UTCEG score recompute
  18. 2026-07-08 21:31 UTCVendor advisory
  19. 2026-07-08 17:53 UTCEG score recompute
  20. 2026-07-08 17:53 UTCVendor advisory
  21. 2026-07-08 15:12 UTCEPSS rescore
  22. 2026-07-08 14:14 UTCEG score recompute
  23. 2026-07-08 14:14 UTCVendor advisory
  24. 2026-07-08 10:36 UTCEG score recompute
  25. 2026-07-08 10:36 UTCVendor advisory
  26. 2026-07-08 06:58 UTCEG score recompute
  27. 2026-07-08 06:58 UTCVendor advisory
  28. 2026-07-08 03:18 UTCEG score recompute
  29. 2026-07-08 03:18 UTCVendor advisory
  30. 2026-07-07 23:39 UTCEG score recompute
  31. 2026-07-07 23:39 UTCVendor advisory
  32. 2026-07-07 20:00 UTCEG score recompute
  33. 2026-07-07 20:00 UTCVendor advisory
  34. 2026-07-07 19:01 UTCCISA KEV update
  35. 2026-07-07 17:16 UTCCISA KEV update
  36. 2026-07-07 16:21 UTCEG score recompute
  37. 2026-07-07 16:21 UTCVendor advisory
  38. 2026-07-07 12:42 UTCEG score recompute
  39. 2026-07-07 12:42 UTCVendor advisory
  40. 2026-07-07 09:03 UTCEG score recompute
  41. 2026-07-07 09:03 UTCVendor advisory
  42. 2026-07-07 05:24 UTCEG score recompute
  43. 2026-07-07 05:24 UTCVendor advisory
  44. 2026-07-07 01:45 UTCEG score recompute
  45. 2026-07-07 01:45 UTCVendor advisory
  46. 2026-07-06 22:06 UTCEG score recompute
  47. 2026-07-06 22:06 UTCVendor advisory
  48. 2026-07-06 18:26 UTCEG score recompute
  49. 2026-07-06 18:26 UTCVendor advisory
  50. 2026-07-06 14:46 UTCEG score recompute
  51. 2026-07-06 14:46 UTCVendor advisory
  52. 2026-07-06 11:07 UTCEG score recompute
  53. 2026-07-06 11:07 UTCVendor advisory
  54. 2026-07-06 07:27 UTCEG score recompute
  55. 2026-07-06 07:27 UTCVendor advisory
  56. 2026-07-06 03:48 UTCEG score recompute
  57. 2026-07-06 03:48 UTCVendor advisory
  58. 2026-07-06 00:08 UTCEG score recompute
  59. 2026-07-06 00:08 UTCVendor advisory
  60. 2026-07-05 20:29 UTCEG score recompute
  61. 2026-07-05 20:29 UTCVendor advisory
  62. 2026-07-05 16:50 UTCEG score recompute
  63. 2026-07-05 16:50 UTCVendor advisory
  64. 2026-07-05 13:10 UTCEG score recompute
  65. 2026-07-05 13:10 UTCVendor advisory
  66. 2026-07-05 09:31 UTCEG score recompute
  67. 2026-07-05 09:31 UTCVendor advisory
  68. 2026-07-05 05:53 UTCEG score recompute
  69. 2026-07-05 05:53 UTCVendor advisory
  70. 2026-07-05 02:13 UTCEG score recompute
  71. 2026-07-05 02:13 UTCVendor advisory
  72. 2026-07-04 22:34 UTCEG score recompute
  73. 2026-07-04 22:34 UTCVendor advisory
  74. 2026-07-04 18:55 UTCEG score recompute
  75. 2026-07-04 18:55 UTCVendor advisory

Publicly available exploits

(10 references)

Working exploit code is in the public domain (2 Metasploit modules) (8 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCzangcc/CVE-2022-22965-rexbb
    First seen Dec 28, 2022

    CVE-2022-22965\Spring-Core-RCE核弹级别漏洞的rce图形化GUI一键利用工具，基于JavaFx开发，图形化操作更简单，提高效率。

    Open source ↗
  • GitHub PoCtpt11fb/SpringVulScan
    First seen Jun 19, 2022

    burpsuite 的Spring漏洞扫描插件。SpringVulScan：支持检测：路由泄露|CVE-2022-22965|CVE-2022-22963|CVE-2022-22947|CVE-2016-4977

    Open source ↗
  • GitHub PoCalt3kx/CVE-2022-22965
    First seen Apr 7, 2022

    Spring Framework RCE (CVE-2022-22965) Nmap (NSE) Checker (Non-Intrusive)

    Open source ↗
  • GitHub PoC4nth0ny1130/spring4shell_behinder
    First seen Apr 7, 2022

    CVE-2022-22965写入冰蝎webshell脚本

    Open source ↗
  • Metasploitexploit/multi/http/spring_framework_rce_spring4shell✓ verified
    First seen Apr 4, 2022

    Spring Framework data-binding RCE via classLoader manipulation.

    Open source ↗
  • GitHub PoCSecNN/SpringFramework_CVE-2022-22965_RCE
    First seen Apr 1, 2022

    SpringFramework 远程代码执行漏洞CVE-2022-22965

    Open source ↗
  • GitHub PoCFourCoreLabs/spring4shell-exploit-poc
    First seen Mar 31, 2022

    Exploit a vulnerable Spring application with the Spring4Shell (CVE-2022-22965) Vulnerability.

    Open source ↗
  • GitHub PoCreznok/Spring4Shell-POC
    First seen Mar 31, 2022

    Dockerized Spring4Shell (CVE-2022-22965) PoC application and exploit

    Open source ↗
  • Metasploitexploit/multi/http/spring_framework_rce_spring4shell✓ verified
    First seen Mar 31, 2022

    Spring Framework Class property RCE (Spring4Shell)

    Open source ↗
  • GitHub PoCTheGejr/SpringShell
    First seen Mar 30, 2022

    Spring4Shell - Spring Core RCE - CVE-2022-22965

    Open source ↗

Past incidents using this CVE

(1)

This CVE was central to one or more publicly-documented breaches. Each card links to authoritative reporting at the time of the incident.

  • Spring4Shell (Spring Framework)Mar 2022

    Spring Framework data-binding flaw allowed RCE on JDK 9+ web apps via classloader manipulation. Initially conflated with a Spring Cloud Function CVE, causing widespread confusion.

    Source: BleepingComputer

Frequently asked(6)

What is CVE-2022-22965?
CVE-2022-22965 is a critical vulnerability published on April 1, 2022. 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…
When was CVE-2022-22965 disclosed?
CVE-2022-22965 was first published in the National Vulnerability Database on April 1, 2022, with the most recent update on October 30, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-22965 actively exploited?
Yes. CISA added CVE-2022-22965 to the Known Exploited Vulnerabilities catalog on April 4, 2022, affecting VMware Spring Framework. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2022-22965?
CVE-2022-22965 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2022-22965?
CVE-2022-22965 affects VMware Spring Framework. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2022-22965?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-22965, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-22965

Explore →

Is Your Infrastructure Affected by CVE-2022-22965?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs