CVE-2022-25762

If a web application sends a WebSocket message concurrently with the WebSocket connection closing when running on Apache Tomcat 8.5.0 to 8.5.75 or Apache Tomcat 9.0.0.M1 to 9.0.20, it is possible that the application will continue to use the socket after it has been closed. The error handling triggered in this case could cause the a pooled object to be placed in the pool twice. This could result in subsequent connections using the same object concurrently which could result in data being returned to the wrong use and/or other errors.

What this means for your business

It affects Apache Tomcat. It matters if your company, or a supplier that handles your data, runs it.
An attacker can use it remotely, over a network, without a login, and without anyone at your company clicking anything.
FIRST's prediction model gives it a 8% chance of attack attempts being seen in the next 30 days, ranking above 94% of all known flaws.

What to do

1Check whether your company or your suppliers run Apache Tomcat, and which version. The affected versions are listed further down this page.
2If you do, apply the vendor's fix. A patch or vendor advisory has been published.

Not sure if your company is exposed?

Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.

Check if you’re exposed Book a call

Scoring

CVSS: 8.6 (v3.1)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Weakness: CWE-404
Assigned by: security@apache.org

Dates

Published: 2022-05-13
Last modified: 2026-08-25
Sources: NVD

Affected products

Apache Tomcat8.5.0 - 8.5.76, 9.0.0 - 9.0.21
Oracle Agile Product Lifecycle Management9.3.6

As listed in the NVD configuration data. Not a statement about your estate.