Skip to main content
VulnerabilityPublished

CVE-2026-118233: Allocation of resources without limits or throttling vulnerability in Apache Tomcat during HTTP

Affects tomcatSource GCVE Database

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

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

Data as of 20 Nov 2026, 01:38 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.29

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

Affected software

ProductAffectedFixed in
Mavenorg.apache.tomcat/tomcatpkg:maven/org.apache.tomcat/tomcatOther threatsAffected
  • >=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
Fixed in–

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

AI-suggested

Upgrade affected Apache Tomcat installations to version 11.0.29, 10.1.62, or 9.0.124 as these versions contain fixes for this vulnerability. No other mitigation or temporary workaround is indicated.

Description

A resource allocation vulnerability in Apache Tomcat occurs during HTTP upgrade handling without limits or throttling, potentially leading to denial of service (DoS). This affects multiple versions including 8.5.61 through 8.5.100, 9.0.41 through 9.0.123, 10.1.0-M1 through 10.1.61, and 11.0.0-M1 through 11.0.27. The issue is fixed in versions 11.0.29, 10.1.62, and 9.0.124. Users should upgrade to these fixed versions to mitigate the vulnerability.

References

Community reviews

Loading reviews…