Quick answers
- Is CVE-2026-93446 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93446 being exploited in the wild.
- How severe is CVE-2026-93446?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Apache Tomcat 9.0.90–9.0.122, 10.1.25–10.1.60, 11.0.0-M21–11.0.26.
- Is there a fix for CVE-2026-93446?
- Yes: fixed in Tomcat 9.0.123, 10.1.61, 11.0.27. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93446 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-93446?
- Check whether you run Apache Tomcat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Tomcat 9.0.123, 10.1.61, 11.0.27
Technical details
An incomplete cleanup vulnerability in Tomcat's TLS 1.3 connection handling leaves resources or state uncleared between requests, causing subsequent connections to fail intermittently. The vulnerability is triggered during normal TLS 1.3 encrypted communications and requires no authentication or special user interaction. Affected versions span 9.0.90–9.0.122, 10.1.25–10.1.60, and 11.0.0-M21–11.0.26.
Affected products
- Apache Tomcat 9.0.90–9.0.122, 10.1.25–10.1.60, 11.0.0-M21–11.0.26
Timeline
- 2026-10-20: disclosed