Skip to main content
Menu
CVEs

Apache Tomcat denial of service in HTTP/2 connection handling

CVE-2026-116830Published November 19, 2026, updated

Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

Apache Tomcat's HTTP/2 initial connection handling fails to release a resource after its useful lifetime ends, which lets an attacker cause a denial of service. Several release lines of Apache Tomcat are affected, and newer releases fix the issue.

Written by a model

Original description

Missing release of resource after effective lifetime vulnerability in Apache Tomcat's HTTP/2 initial connection handling leads to 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.20 through 9.0.123.

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

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-116830 (Apache Tomcat: HTTP/2 checks frame type before size leads to DoS), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-116830 (entry last updated 2026-11-19):
Affected:
- Apache Software Foundation Apache Tomcat: from 11.0.0-M1, through 11.0.27; from 10.1.0-M1, through 10.1.61; from 9.0.20, through 9.0.123
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-116830 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116830 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/dsnks241sjb4fl3v3kl86fg24m1yspk6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-116830
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-116830"}.

Affected versions

cve.now Index

5Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 60 if added to CISA KEV
  • Would score about 55 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisorylists.apache.org · thread.html/dsnks241sjb4fl3v3kl86fg24m1yspk6
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-116830
RecordNVD · CVE-2026-116830

Questions about CVE-2026-116830

Is CVE-2026-116830 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-116830?

Apache Tomcat: from 11.0.0-M1 through 11.0.27; from 10.1.0-M1 through 10.1.61; from 9.0.20 through 9.0.123.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.