Skip to content
Server Security Center
KEVcritical9.8

CVE-2022-22965: Spring Framework JDK 9+ Remote Code Execution

VMware Spring Framework · listed in the CISA catalog of actively exploited vulnerabilities since 2022-04-04.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
99.6%
among the highest 0.1% of all CVEs
Added to CISA KEV
2022-04-04
US federal due date 2022-04-25
Ubuntu priority
high

CVE-2022-22965 explained

CVE-2022-22965 is a remote code execution flaw in VMware Spring Framework affecting Spring MVC or Spring WebFlux applications on JDK 9+ through data binding. The known exploit requires a Tomcat WAR deployment, but the underlying issue is more general. It is listed in CISA's Known Exploited Vulnerabilities catalog.

Impact

An unauthenticated remote attacker can execute code in a vulnerable application over the network, with low complexity and no user interaction. This can fully compromise confidentiality, integrity and availability. The specific exploit needs the application to run on JDK 9+ and on Tomcat as a WAR deployment. Spring Boot executable jars, the default, are not vulnerable to that exploit. Other ways to exploit the flaw may exist.

Who is affected

The source package is libspring-java. On Ubuntu, fixes are available only through Ubuntu Pro (ESM): 18.04 LTS (4.3.22-1~18.04.1~esm1), 20.04 LTS (4.3.22-4ubuntu0.1~esm1), 22.04 LTS (4.3.30-1ubuntu0.1~esm1) and 24.04 LTS (4.3.30-2ubuntu0.24.04.1~esm1). Ubuntu 25.10 has 4.3.30-2ubuntu1 in the standard archive but is end of life. Debian 12 (bookworm), Debian 13 (trixie) and the testing distribution Debian 14 (forky) have no fix; Debian rates the issue unimportant and plans none.

Written with AI from the data on this page and checked against it automatically.

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

CISA required action: Apply updates per vendor instructions.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • Spring Framework
    Affected
    • Spring Framework versions 5.3.X prior to 5.3.18+, 5.2.x prior to 5.2.20+ and all old and unsupported versions
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Identify Spring MVC or WebFlux applications running on JDK 9+, especially those deployed as WAR files on Tomcat.
  2. On Ubuntu LTS releases, enable Ubuntu Pro (ESM) and update libspring-java to the listed fixed version.
  3. Restart Java applications and application servers that use the library so they load the patched code.
  4. Upgrade systems running end-of-life Ubuntu 25.10 to a supported release.
  5. For applications bundling their own Spring Framework, follow the VMware advisory and update the bundled copy.

Debian 12 (bookworm), Debian 13 (trixie) and Debian 14 (forky) have no fixed libspring-java and none is planned. Check whether any application actually uses this package on JDK 9+. Where possible, avoid Tomcat WAR deployments of affected applications, restrict network access to them, and follow the VMware advisory for updated Spring Framework versions.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace libspring-java with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="libspring-java"'

2. Compare each installed version with the fixed version for your release from the table (releases with a fixed version only)

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="libspring-java"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

No fixed version yet on 3 releases

Debian 14 (forky), Debian 13 (trixie), Debian 12 (bookworm): no fixed version of libspring-java yet, so every installed version there is affected. Until a fix is published:

  • Follow the vendor's advisory for a mitigation or patch: tanzu.vmware.com/security/cve-2022-22965
  • If the server does not need the package, remove it, or replace it with a maintained alternative.
  • Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.

This page updates automatically when Ubuntu or Debian publish a fix.

Rows marked “fix via Ubuntu Pro”: these fixes are only installable with an Ubuntu Pro subscription (ESM). Attach the machine first (sudo pro attach, then sudo pro enable esm-infra esm-apps), then run the commands above.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-94 Improper Control of Generation of Code ('Code Injection')

Questions about CVE-2022-22965

Is my Spring Boot application vulnerable?
Applications deployed as Spring Boot executable jars, the default, are not vulnerable to the known exploit. The known exploit requires JDK 9+ and a Tomcat WAR deployment. The vendor notes the flaw is more general, so other exploitation paths may exist; updating remains advisable.
Why can't I get the Ubuntu fix from the normal archive?
For Ubuntu 18.04, 20.04, 22.04 and 24.04 LTS, the fixed libspring-java packages are published only through Ubuntu Pro (ESM). An Ubuntu Pro subscription is needed to install them.
Is this vulnerability exploited in practice?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-04-04 and requires applying updates per vendor instructions. Ransomware use is listed as unknown.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.