Skip to content
VulniPulse
Low 2 vendors · 2 advisories

CVE-2026-118233: Apache Tomcat: Memory leak on HTTP upgrade leads to DoS

CVE-2026-118233 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Low
Weakness
  • CWE-770 Allocation of resources without limits or throttling
Fixed releases
  • Apache: 11.0.29, 10.1.62, 9.0.124
Vendor advisories
2 from Apache, Red Hat
Assigned by
apache (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-118233; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

Allocation of resources without limits or throttling vulnerability in Apache Tomcat during HTTP upgrade in some circumstances lead to possible DoS. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 through 10.1.61, from 9.0.41 through 9.0.123. The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.61 through 8.5.100. Other unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124, which fix the issue. Note: Tomcat 11.0.28 was not released

Text from the CVE.org record (apache).

How do I fix CVE-2026-118233?

Upgrade to a fixed release named by the vendor:

  • Apache: 11.0.29, 10.1.62, 9.0.124
  • Allocation of resources without limits or throttling vulnerability in Apache Tomcat during HTTP upgrade in some circumstances lead to possible DoS. (Apache)
  • Users are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124, which fix the issue. (Apache)
  • Restrict network access to the Apache Tomcat service to trusted networks or bind it locally behind a reverse proxy to minimize exposure to untrusted HTTP upgrade traffic. 1. Restrict external network reachability using firewalld to allow only trusted subnets to reach the Tomcat port (e.g., 8080): # firewall-cmd --permanent --zone=public --remove-port=8080/tcp # firewall-cmd --permanent --zone=trusted --add-source=192.168.1.0/24 # firewall-cmd --reload 2. Alternatively, if Tomcat is deployed alongside a local reverse proxy, restrict the HTTP connector to localhost by editing the Connector configuration in server.xml: Then restart the Tomcat service: # systemctl restart tomcat Caveats: Restricting access to trusted networks will prevent unauthorized remote clients from accessing applications hosted on the instance. Binding the connector to localhost requires a local reverse proxy (such as Apache HTTP Server) to route client requests. Warning: Reloading the firewall with firewall-cmd --reload may interrupt existing active connections. Restarting the Tomcat service with systemctl restart tomcat will terminate active user sessions and cause temporary service downtime. (Red Hat)

Vendor advisories for CVE-2026-118233

Apache

1 advisory
  • Advisory severityLow

    Low [CVE-2026-118233] Allocation of resources without limits or throttling vulnerability in Apache Tomcat during HTTP upgrade in some circumstances lead to possible DoS

    CVE-2026-118233Source published Source updated

    Allocation of resources without limits or throttling vulnerability in Apache Tomcat during HTTP upgrade in some circumstances lead to possible DoS. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 through 10.1.61, from 9.0.41 through 9.0.123. The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.61 through 8.5.100. Other unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124, which fix the issue. Note: Tomcat 11.0.28 was not released

    Affected products in this advisory
    • Apache Tomcat
    Source-reported affected versions
    • 11.0.0-M1 through 11.0.27
    • 10.1.0-M1 through 10.1.61
    • 9.0.41 through 9.0.123.
    • 8.5.61 through 8.5.100.

    2 more entries in the full advisory.

    Source-reported fixed versions
    • 11.0.29
    • 10.1.62
    • 9.0.124
    Mitigation guidance
    • Allocation of resources without limits or throttling vulnerability in Apache Tomcat during HTTP upgrade in some circumstances lead to possible DoS.
    • Users are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124, which fix the issue.

Red Hat

1 advisory
  • Advisory severityLow

    Low [CVE-2026-118233] Denial of Service via HTTP upgrade

    CVE-2026-118233Source published Source updated

    Denial of Service via HTTP upgrade. Red Hat rates this low. Weakness: CWE-770. Affected product named by the advisory: Red Hat Hardened Images.

    Related products — impact not confirmed
    • Red Hat Hardened Images
    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    • Restrict network access to the Apache Tomcat service to trusted networks or bind it locally behind a reverse proxy to minimize exposure to untrusted HTTP upgrade traffic. 1. Restrict external network reachability using firewalld to allow only trusted subnets to reach the Tomcat port (e.g., 8080): # firewall-cmd --permanent --zone=public --remove-port=8080/tcp # firewall-cmd --permanent --zone=trusted --add-source=192.168.1.0/24 # firewall-cmd --reload 2. Alternatively, if Tomcat is deployed alongside a local reverse proxy, restrict the HTTP connector to localhost by editing the Connector configuration in server.xml: <Connector port="8080" protocol="HTTP/1.1" address="127.0.0.1" connectionTimeout="20000" redirectPort="8443" /> Then restart the Tomcat service: # systemctl restart tomcat Caveats: Restricting access to trusted networks will prevent unauthorized remote clients from accessing applications hosted on the instance. Binding the connector to localhost requires a local reverse proxy (such as Apache HTTP Server) to route client requests. Warning: Reloading the firewall with firewall-cmd --reload may interrupt existing active connections. Restarting the Tomcat service with systemctl restart tomcat will terminate active user sessions and cause temporary service downtime.

References

Timeline

  1. CVE record published
  2. First vendor advisory listed by VulniPulse

All Apache advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache