Skip to main content
VulnerabilityPublished

CVE-2026-116600: Apache Tomcat · Memory Leak

Affects Apache TomcatSource CVE Database V5

0
Compare

Not known to be exploited.

Data as of 19 Nov 2026, 21:37 UTC

Severity
Medium

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

Thin evidence

One scorer or none

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
Apache Software FoundationApache TomcatAffected
  • >=11.0.0-M1 <=11.0.27
  • >=10.1.0-M1 <=10.1.61
  • >=9.0.22 <=9.0.123
  • >=8.5.0 <=8.5.100
  • >=7.0.43 <=7.0.109
Fixed in–
Mavenorg.apache.tomcat/tomcatpkg:maven/org.apache.tomcat/tomcatOther threatsAffected
  • 7.0.43 – 11.0.27
10 affected builds
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 affected Apache Tomcat versions to 11.0.29, 10.0.62, or 9.0.124, which contain fixes for this memory leak. Since this is a resource management issue, patching is the recommended mitigation. No other vendor advisories indicate alternative mitigations or that no action is required.

Description

A memory leak vulnerability exists in Apache Tomcat's WebSocket implementation, where memory is not released after its effective lifetime. This affects multiple versions across Tomcat 7, 8.5, 9, 10.1, and 11. Users are advised to upgrade to fixed versions 11.0.29, 10.0.62, or 9.0.124 to resolve the issue.

References

Community reviews

Loading reviews…