Apache Tomcat: Denial of Service via HTTP/2 connection resource exhaustion (CVE-2026-116830)
Apache Tomcat is vulnerable to a denial of service (DoS) condition due to improper resource management in HTTP/2 initial connection handling, allowing an attacker to exhaust system resources.
CVE search metadata
CVE search record: CVE-2026-116830. Severity: high. CVSS: 7.5. EPSS: 0.15%. KEV: no. Product: Tomcat. Brief: Apache Tomcat: Denial of Service via HTTP/2 connection resource exhaustion (CVE-2026-116830). Brief link: https://feed.craftedsignal.io/briefs/2026-11-tomcat-dos-cve-2026-116830/
Triage facts
Revision 1- Applicability
- Tomcat
- Evidence
- Unknown
- Severity
- Low
- Action
- Elevated
- Sources
- 2 public sources
- Freshness
- Revision 1Nov 20, 20:59 UTC
- Vulnerabilities
- 1 CVE
- Source quality
- A1
Overview
Apache Tomcat contains a vulnerability where system resources are not correctly released following the effective lifetime of an HTTP/2 initial connection. This flaw allows a remote, unauthenticated attacker to trigger a denial-of-service condition by exhausting server resources through specifically crafted or excessive HTTP/2 connection attempts. Tomcat 11.0.28 was not released as part of the remediation cycle.
Impact
Successful exploitation leads to a denial-of-service, rendering the affected Tomcat instance unable to process incoming requests.
Recommendation
Deploy the following updates to address CVE-2026-116830:
- Upgrade Apache Tomcat 11.x to version 11.0.29 or later.
- Upgrade Apache Tomcat 10.1.x to version 10.1.62 or later.
- Upgrade Apache Tomcat 9.0.x to version 9.0.124 or later.
Threat Hunt
Identify abnormal spikes or consistent high-volume HTTP/2 connection attempts originating from single source IP addresses targeting Apache Tomcat instances, specifically looking for abandoned or unclosed connection threads that remain in a hanging state.
Data: Web server access logs, Application server performance metrics, Connection thread state telemetry
Mitigations
Upgrade to the specified patched versions of Apache Tomcat for each respective branch
Gaps
- Lack of specific WAF/IDS signature guidance for HTTP/2 resource exhaustion patterns