Server crash via unbounded WebSocket message backlog
Published Jul 28, 2026 · Updated Jul 28, 2026
Uncontrolled resource consumption in Apache Tomcat's WebSocket chat example allows remote attackers to crash the server process. ChatAnnotation queues every broadcast in messageBacklog while an asynchronous send to a slow client remains in progress, without bounding the queue. The unauthenticated attack requires the examples web application to remain deployed and can exhaust heap memory until the Tomcat process fails.
Summary
What happened
Uncontrolled resource consumption in Apache Tomcat's WebSocket chat example allows remote attackers to crash the server process. ChatAnnotation queues every broadcast in messageBacklog while an asynchronous send to a slow client remains in progress, without bounding the queue. The unauthenticated attack requires the examples web application to remain deployed and can exhaust heap memory until the Tomcat process fails.
The record
- CVE
- CVE-2026-66299
- Published
- Jul 28, 2026
- Updated
- Jul 28, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Tomcat
- Classifications
- CWE-400, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2026CVE publishedPublication date reported by the CVE source.
- Jul 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.1.24 <=10.1.57
- Affected versionversion=11.0.0-M20 <=11.0.24
- Affected versionversion=9.0.89 <=9.0.120
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo