You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Mark Thomas <ma...@apache.org> on 2026/07/28 14:26:56 UTC
[SECURITY] CVE-2026-66299 Apache Tomcat - DoS via WebSocket chat example
CVE-2026-66299 Apache Tomcat - DoS via WebSocket chat example
Severity: Low
Vendor: The Apache Software Foundation
Versions Affected:
Apache Tomcat 11.0.0-M20 to 11.0.24
Apache Tomcat 10.1.24 to 10.1.57
Apache Tomcat 9.0.89 to 9.0.120
Description:
The WebSocket chat example provided an unbounded buffer for undelivered
messages. A maliciously slow client could cause the buffer to grow
continuously, eventually leading to an memory exhaustion and failure of
the Tomcat process.
Mitigation:
Users of the affected versions should apply one of the following
mitigations:
- Remove the examples web application
- Upgrade to Apache Tomcat 11.0.25 or later when released
- Upgrade to Apache Tomcat 10.1.58 or later when released
- Upgrade to Apache Tomcat 9.0.121 or later when released
Credit:
This issue was identified by:
- 4ra1n, pyn3rd and unam4
History:
2026-07-28 Original advisory
References:
[1] https://tomcat.apache.org/security-11.html
[2] https://tomcat.apache.org/security-10.html
[3] https://tomcat.apache.org/security-9.html
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [SECURITY] CVE-2026-66299 Apache Tomcat - DoS via WebSocket chat example
Posted by Mark Thomas <ma...@apache.org>.
On 28/07/2026 15:26, Mark Thomas wrote:
> CVE-2026-66299 Apache Tomcat - DoS via WebSocket chat example
<snip/>
The majority of the subscribers here aren't part of the Tomcat security
team so we wanted to make everyone aware of some of the discussions the
security team had about this issue.
Given that this issue shouldn't affect anyone (everyone has followed the
advice to remove the examples web application for production - right?),
we wanted to use this as an experiment to see how the community reacted
to us publishing a CVE that they should not be impacted by when they
can't currently obtain a release with a fix for the CVE.
One of the ideas floated in various OSS projects to help manage the
flood of AI generated vulnerability reports - particularly where it is
highly unlikely any users will be affected - is to fix and publish
without a release. The purpose of this experiment is to see what that
might look like for the Tomcat community.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org