CVE-2026-116600
Patch Available.
This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.
Overview
Apache Tomcat is an open-source implementation of the Jakarta Servlet, Jakarta Pages, Jakarta Expression Language, Jakarta WebSocket, Jakarta Annotations, and Jakarta Authentication specifications. It serves Java web applications either as a standalone servlet container and HTTP server or embedded inside an application through the tomcat-embed-core artifact. Its Catalina servlet container (org.apache.tomcat:tomcat-catalina) supplies the request-processing pipeline, including Valves such as RewriteValve, along with connectors, realms, and session management.
A denial of service vulnerability (CVE-2026-116600) has been identified in the Apache Tomcat WebSocket implementation, which allows attackers to exhaust server memory by opening WebSocket connections whose endpoint and encoder instances are never released by the container's instance manager. The leak is reachable when Tomcat is used with an instance manager that tracks the instances it creates, such as the OpenWebBeans (OWB) integration.
Per OWASP: The Denial of Service (DoS) attack is focused on making a resource (site, application, server) unavailable for the purpose it was designed.
This issue affects multiple versions of Apache Tomcat.
Details
Module Info
- Product: Apache Tomcat
- Affected packages:
org.apache.tomcat:tomcat-websocket,org.apache.tomcat.embed:tomcat-embed-websocket - Affected versions: >=7.0.43 <=7.0.109, >=8.5.0 <=8.5.100, >=9.0.22 <=9.0.123, >=10.1.0-M1 <=10.1.61, >=11.0.0-M1 <=11.0.27
- GitHub repository: https://github.com/apache/tomcat
- Published packages: https://central.sonatype.com/artifact/org.apache.tomcat/tomcat-websocket, https://central.sonatype.com/artifact/org.apache.tomcat.embed/tomcat-embed-websocket
- Package manager: Maven
- Fixed in:
- OSS Apache Tomcat 9.0.124, 10.1.62, 11.0.29
Vulnerability Info
This High-severity vulnerability is found in the org.apache.tomcat:tomcat-websocket package (and its embedded counterpart org.apache.tomcat.embed:tomcat-embed-websocket) in multiple versions of Apache Tomcat.
When a WebSocket session is created, Tomcat asks the web application's InstanceManager to create (or register) the endpoint instance and one instance of every configured Encoder. An instance manager that performs dependency injection, such as the OpenWebBeans integration, keeps per-instance state for each object it creates, and that state is only released when the same object is later passed back to InstanceManager.destroyInstance(). Several paths in the WebSocket implementation never hand those objects back.
When the session closes, WsSession.fireEndpointOnClose() passes the session's localEndpoint to the instance manager. For an annotated POJO endpoint, localEndpoint is the PojoEndpointServer wrapper that Tomcat builds around the POJO, not the POJO instance the instance manager created, so the manager does not recognise it and the POJO's state is never released:
if (endpointInstance instanceof Endpoint) {
this.localEndpoint = (Endpoint) endpointInstance;
} else {
this.localEndpoint = new PojoEndpointServer(pathParameters, endpointInstance);
}
// ...
} finally {
if (instanceManager != null) {
try {
instanceManager.destroyInstance(localEndpoint);
} catch (Throwable t2) {Session setup failures leak in the same way. WsRemoteEndpointImplBase.setEncoders() creates each encoder through the instance manager and calls init() on it, but if an encoder's construction or initialisation fails, the encoders already created are never destroyed. Likewise, if the endpoint instance cannot be created after the encoders were set up, or if creating the WebSocket frame handler or the endpoint's onOpen() method throws in WsHttpUpgradeHandler.init() (or in the client's WsWebSocketContainer), the session is never registered with the container and is never closed, so neither the endpoint nor its encoders are released:
for (Class<? extends Encoder> encoderClazz : endpointConfig.getEncoders()) {
Encoder instance;
InstanceManager instanceManager = wsSession.getInstanceManager();
try {
if (instanceManager == null) {
instance = encoderClazz.getConstructor().newInstance();
} else {
instance = (Encoder) instanceManager.newInstance(encoderClazz);
}
instance.init(endpointConfig);
} catch (ReflectiveOperationException | NamingException e) {
throw new DeploymentException(sm.getString("wsRemoteEndpoint.invalidEncoder", encoderClazz.getName()),
e);
}
EncoderEntry entry = new EncoderEntry(Util.getEncoderType(encoderClazz), instance);
encoderEntries.add(entry);
}In addition, in Tomcat versions that ship the OWB module, its OpenWebBeansInstanceManager looks up the tracked instance with instances.get(object) in destroyInstance() and never removes it from its ConcurrentHashMap, so even instances that are destroyed correctly stay referenced:
Instance injectorInstance = instances.get(object);Each leaked entry keeps the endpoint or encoder object and its CDI creational context reachable for the lifetime of the web application. A remote client that repeatedly opens and closes WebSocket connections to such an application, for example to an annotated POJO endpoint, steadily grows this retained memory until the server exhausts its heap and stops serving requests.
Mitigation
Only recent versions of Apache Tomcat are community-supported. The community support version will not receive any updates to address this issue. For more information, see here.
Users of the affected components should apply one of the following mitigations:
- Upgrade to a patched version of Apache Tomcat.
- Leverage a commercial support partner like HeroDevs for post-EOL security support.