# CVE-2022-25762: Response mix-up with WebSocket concurrent send and close

> A race condition in Apache Tomcat WebSocket handling can cause data leakage to wrong users or service errors.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 May 2022
- **Updated:** 8 Oct 2026
- **Also known as:** BIT-tomcat-2022-25762, DEBIAN-CVE-2022-25762, GHSA-h3ch-5pp2-vh6w, UBUNTU-CVE-2022-25762

## What is CVE-2022-25762?

CVE-2022-25762 is a high-severity vulnerability in Apache Tomcat, published on 13 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2022-25762?

5 open source packages ship an affected version, including org.apache.tomcat:tomcat and tomcat. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.75 |
| `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.75 |
| `org.apache.tomcat:tomcat` | Maven | From 9.0.0M1 | 9.0.20 |
| `org.apache.tomcat:tomcat` | Maven | From 9.0.0M1 | 9.0.20 |
| `tomcat` | Bitnami | From 8.5.0 | 8.5.76, 9.0.21 |

Products: Apache Tomcat, Oracle Agile Product Lifecycle Management.

## How do I fix CVE-2022-25762?

Upgrade org.apache.tomcat:tomcat to a fixed version for your release line: 8.5.75 or 9.0.20.

## Is CVE-2022-25762 being exploited?

There is no known exploitation of CVE-2022-25762 in the wild and no public exploit code.

## Other vulnerabilities in Apache Tomcat

- [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild)
- [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25762 and fix it if it is affected.

What it is: CVE-2022-25762 is a high-severity vulnerability in Apache Tomcat, published on 13 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25762 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.75
- org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.75
- org.apache.tomcat:tomcat (Maven): affected from 9.0.0M1; fixed in 9.0.20
- org.apache.tomcat:tomcat (Maven): affected from 9.0.0M1; fixed in 9.0.20
- tomcat (Bitnami): affected from 8.5.0; fixed in 8.5.76, 9.0.21

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-25762/ (Markdown: https://insights.sbomify.com/CVE-2022-25762/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-25762
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-25762
- OSV: https://osv.dev/vulnerability/CVE-2022-25762

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-25762/
Summaries are generated and may contain mistakes; the official description above is the record.