Denial of Service via incomplete cleanup vulnerability in Apache TomcatGHSA-v682-8vv8-vpwr
MEDIUMFix: apache/tomcat@0052b37GHSA-v682-8vv8-vpwr is a medium-severity (CVSS 6.3) CWE-459 vulnerability in org.apache.tomcat:tomcat-websocket. A fix is available for org.apache.tomcat:tomcat-websocket — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-v682-8vv8-vpwr.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.tomcat:tomcat-websocket☕org.apache.tomcat:tomcat-websocket☕org.apache.tomcat:tomcat-websocket☕org.apache.tomcat:tomcat-websocket☕org.apache.tomcat.embed:tomcat-embed-websocket☕org.apache.tomcat.embed:tomcat-embed-websocket☕org.apache.tomcat.embed:tomcat-embed-websocket☕org.apache.tomcat.embed:tomcat-embed-websocketReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Denial of Service via incomplete cleanup vulnerability in Apache Tomcat. It was possible for WebSocket clients to keep WebSocket connections open leading to increased resource consumption.This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M16, from 10.1.0-M1 through 10.1.18, from 9.0.0-M1 through 9.0.85, from 8.5.0 through 8.5.98.
Older, EOL versions may also be affected.
Users are recommended to upgrade to version 11.0.0-M17, 10.1.19, 9.0.86 or 8.5.99 which fix the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat:tomcat-websocket | ≥ 11.0.0-M1&&< 11.0.0-M17 | 11.0.0-M17org.apache.tomcat:tomcat-websocket:11.0.0-M17 |
| ☕Maven | org.apache.tomcat:tomcat-websocket | ≥ 10.1.0-M1&&< 10.1.19 | 10.1.19org.apache.tomcat:tomcat-websocket:10.1.19 |
| ☕Maven | org.apache.tomcat:tomcat-websocket | ≥ 9.0.0-M1&&< 9.0.86 | 9.0.86org.apache.tomcat:tomcat-websocket:9.0.86 |
| ☕Maven | org.apache.tomcat:tomcat-websocket | ≥ 8.5.0&&< 8.5.99 | 8.5.99org.apache.tomcat:tomcat-websocket:8.5.99 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-websocket | ≥ 11.0.0-M1&&< 11.0.0-M17 | 11.0.0-M17org.apache.tomcat.embed:tomcat-embed-websocket:11.0.0-M17 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-websocket | ≥ 10.1.0-M1&&< 10.1.19 | 10.1.19org.apache.tomcat.embed:tomcat-embed-websocket:10.1.19 |
Affected Products
tomcatapachedebian linuxdebianfedorafedoraprojectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-websocket, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat-websocket to 11.0.0-M17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v682-8vv8-vpwr is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This Denial of Service (DoS) vulnerability within the Apache Tomcat package represents an Important severity issue due to its potential to significantly impact system availability and performance. By allowing WebSocket clients to maintain open connections without proper cleanup, the vulnerability facilitates the…
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for GHSA-v682-8vv8-vpwr (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | tomcat-1:10.1.36-1.el10_0 | RHSA-2025:7497 |
| Red Hat Enterprise Linux 8 | tomcat-1:9.0.87-1.el8_10.1 | RHSA-2024:3666 |
| Red Hat Enterprise Linux 8.8 Extended Update Support | tomcat-1:9.0.87-1.el8_8.2 | RHSA-2024:3814 |
| Red Hat Enterprise Linux 9 | tomcat-1:9.0.87-1.el9_4.1 | RHSA-2024:3307 |
| Red Hat Enterprise Linux 9.2 Extended Update Support | tomcat-1:9.0.87-1.el9_2.1 | RHSA-2024:3308 |
| Red Hat JBoss Web Server 5 | tomcat | RHSA-2024:1914 |
| Red Hat JBoss Web Server 5.8 on RHEL 7 | jws5-tomcat-0:9.0.87-3.redhat_00003.1.el7jws | RHSA-2024:1913 |
| Red Hat JBoss Web Server 6 | tomcat | RHSA-2024:1917 |
Frequently Asked Questions
Is GHSA-v682-8vv8-vpwr in your dependencies?
Find it across Maven, including transitive dependencies.