Skip to main content
CVE-2026-118436VulnerabilityPublished

Allocation of resources without limits or throttling vulnerability in Apache Tomcat in the CGI Servlet when handling

Affects apache-tomcatSource GCVE Database

0
Compare
Authoritative record:CVE-2026-118436· High

Not known to be exploited : upgrade to 11.0.29 or 11.0.28 soon.

Data as of 20 Nov 2026, 01:39 UTC

Severity
High

Rated High 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, 11.0.28

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/apache-tomcat to 11.0.29 or 11.0.28.

Affected software

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

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 affected Apache Tomcat installations to versions 11.0.29, 10.1.62, or 9.0.124, which contain fixes for this vulnerability. No other mitigation or temporary workaround is indicated in the available data.

Description

A resource allocation vulnerability exists in Apache Tomcat's CGI Servlet when handling POST request bodies, which can lead to denial of service (DoS) for certain inputs. This affects multiple versions across Tomcat 7, 8.5, 9, 10.1, and 11 branches. The issue is fixed in versions 11.0.29, 10.1.62, and 9.0.124. Users should upgrade to these versions to mitigate the risk.

References

Community reviews

Loading reviews…