CVE-2026-118233

Denial of Service
Affects
Apache Tomcat
in
Apache Tomcat
No items found.
Versions
>=8.5.61 <=8.5.100, >=9.0.41 <=9.0.123, >=10.1.0-M1 <=10.1.61, >=11.0.0-M1 <=11.0.27

Patch Available.

Exclamation circle icon
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 (DoS) vulnerability (CVE-2026-118233) has been identified in the HTTP/1.1 upgrade handling of Apache Tomcat, which allows attackers to make the server leak memory by sending requests that reach an HTTP upgrade that then fails. Each failed upgrade leaves an HttpUpgradeHandler instance that is never destroyed, and repeated requests can exhaust server resources.

Per OWASP: The Denial of Service (DoS) attack is focused on making a resource (site, application, server) unavailable for the purpose it was designed. There are many ways to make a service unavailable for legitimate users by manipulating network packets, programming, logical, or resources handling vulnerabilities, among others.

This issue affects multiple versions of Apache Tomcat.

Details

Module Info

Vulnerability Info

This Low-severity vulnerability is found in the org.apache.tomcat:tomcat-coyote package in multiple versions of Apache Tomcat, with the request-side part in org.apache.tomcat:tomcat-catalina (both are shipped in org.apache.tomcat.embed:tomcat-embed-core). It is classified as CWE-770, Allocation of Resources Without Limits or Throttling.

When a servlet calls HttpServletRequest.upgrade(), Request.upgrade() creates the HttpUpgradeHandler instance straight away, through the web application's InstanceManager for application handlers, and hands it to the connector. It does not check whether async processing has already started on the request or whether the response has already been committed:

public <T extends HttpUpgradeHandler> T upgrade(Class<T> httpUpgradeHandlerClass)
        throws IOException, ServletException {
    T handler;
    InstanceManager instanceManager = null;
    try {
        if (InternalHttpUpgradeHandler.class.isAssignableFrom(httpUpgradeHandlerClass)) {
            handler = httpUpgradeHandlerClass.getConstructor().newInstance();
        } else {
            instanceManager = getContext().getInstanceManager();
            handler = (T) instanceManager.newInstance(httpUpgradeHandlerClass);
        }
    } catch (ReflectiveOperationException | NamingException | IllegalArgumentException | SecurityException e) {
        throw new ServletException(e);
    }
    UpgradeToken upgradeToken = new UpgradeToken(handler, getContext(), instanceManager,
            getUpgradeProtocolName(httpUpgradeHandlerClass));

    coyoteRequest.action(ActionCode.UPGRADE, upgradeToken);

    response.setStatus(HttpServletResponse.SC_SWITCHING_PROTOCOLS);

    return handler;
}

In Http11Processor, the UPGRADE action only stores the token and stops further HTTP output:

protected final void doHttpUpgrade(UpgradeToken upgradeToken) {
    this.upgradeToken = upgradeToken;
    // Stop further HTTP output
    outputBuffer.responseFinished = true;
}

From this point the connector treats the connection as upgraded. Nothing checks, before the response headers are written, that the response still carries status 101 and an Upgrade header, or that the request has not ended in an error. When the application later changes the status, never sets the Upgrade header, throws an exception after calling upgrade(), or mixes the upgrade with async processing, the upgrade fails. The handler instance that was created and registered through the InstanceManager is then never passed to destroyInstance(), so it and the resources it holds are not released. Every request that reaches such a failed upgrade leaks one handler instance, and an attacker who can repeatedly trigger that code path can grow memory use until the server can no longer serve 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.
Vulnerability Details
Severity
Level
CVSS Assessment
Low
>=0 <4
Medium
>=4 <6
High
>=6 <8
Critical
>=8 <10
Low
ID
CVE-2026-118233
PROJECT Affected
Apache Tomcat
Versions Affected
>=8.5.61 <=8.5.100, >=9.0.41 <=9.0.123, >=10.1.0-M1 <=10.1.61, >=11.0.0-M1 <=11.0.27
NES Versions Affected
Published date
November 20, 2026
≈ Fix date
Category
Denial of Service
Vex Document
Download VEXHow do I use it?
Sign up for the latest vulnerability alerts fixed in
NES for Apache Tomcat
Rss feed icon
Subscribe via RSS
or

By submitting the form I acknowledge receipt of our Privacy Policy.

Thanks for signing up for our Newsletter! We look forward to connecting with you.
Oops! Something went wrong while submitting the form.