Skip to main content
VulnerabilityPublished

CVE-2026-116830: Missing release of resource after effective lifetime vulnerability in Apache Tomcat's HTTP/2 initial

Affects tomcatSource GCVE Database

0
Compare
Authoritative record:CVE-2026-116830· Medium

Not known to be exploited · fixed in 11.0.28 : update tomcat when convenient.

Data as of 20 Nov 2026, 01:39 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 11.0.28, 10.1.62, 9.0.124

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade org.apache.tomcat/tomcat to 11.0.28, 10.1.62 or 9.0.124.

Affected software

ProductAffectedFixed in
Mavenorg.apache.tomcat/tomcatpkg:maven/org.apache.tomcat/tomcatOther threatsAffected
  • >=11.0.0-M1 <11.0.28
  • >=10.1.0-M1 <10.1.62
  • >=9.0.20 <9.0.124
Fixed in
  • 11.0.28
  • 10.1.62
  • 9.0.124

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to Apache Tomcat versions 11.0.29, 10.1.62, or 9.0.124 to remediate this vulnerability. These versions contain the official fix. No other mitigation is indicated.

Description

A resource release flaw in Apache Tomcat's HTTP/2 initial connection handling can lead to denial of service (DoS). This affects Tomcat versions from 11.0.0-M1 through 11.0.27, 10.1.0-M1 through 10.1.61, and 9.0.20 through 9.0.123. The issue is fixed in versions 11.0.29, 10.1.62, and 9.0.124.

References

Community reviews

Loading reviews…