Skip to main content
CVE-2026-116561VulnerabilityPublished

Apache Tomcat meant · Improper Cleanup on Thrown Exception Vulnerability

Source GCVE Database

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

Not known to be exploited · end of life, no fix coming : replace or isolate Apache Tomcat; no fix will be released.

Data as of 20 Nov 2026, 01:49 UTC

Severity
Medium

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

Thin evidence

One scorer or none
Patch
None coming – the product is end of life

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

No fix will be released: Apache Tomcat is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache TomcatAffected
  • >=11.0.0-M1 <=11.0.27
  • >=10.1.0-M1 <=10.1.61
  • >=9.0.0.M1 <=9.0.123
  • >=8.5.0 <=8.5.100
Fixed in–
Mavenorg.apache.tomcat/tomcatpkg:maven/org.apache.tomcat/tomcatOther threatsAffected
  • >=11.0.0-M1 <=11.0.27
  • >=10.1.0-M1 <=10.1.61
  • >=9.0.0.M1 <=9.0.123
  • 8.5.0 <=8.5.100
Fixed in–

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.0.62, or 9.0.124, which contain fixes for this issue. Since fixed versions are available, applying these official updates is the recommended remediation.

Description

A vulnerability in Apache Tomcat causes improper cleanup when an AuthException is thrown during Jakarta Authentication secureResponse(), resulting in an HTTP 200 response being sent instead of the correct HTTP 500 error response. This affects multiple versions of Apache Tomcat, including 11.0.0-M1 through 11.0.27, 10.1.0-M1 through 10.1.61, and 9.0.0-M1 through 9.0.123, as well as some end-of-life versions. Fixed versions are available.

References

Community reviews

Loading reviews…