Quick answers
- Is CVE-2026-101356 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101356 being exploited in the wild.
- How severe is CVE-2026-101356?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Apache Tomcat 11.0.22–11.0.26, 10.1.55–10.1.60, 9.0.118–9.0.122.
- Is there a fix for CVE-2026-101356?
- Yes: fixed in Tomcat 11.0.27, 10.1.61, 9.0.123. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-101356 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-101356?
- 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 11.0.27, 10.1.61, 9.0.123
Technical details
An incorrect object recycling and re-use vulnerability in Apache Tomcat's HTTP/2 handling of asynchronous servlets can cause request and response objects to be confused or mixed between concurrent users. The issue affects versions 11.0.22–11.0.26, 10.1.55–10.1.60, and 9.0.118–9.0.122. This is a logic flaw in the servlet container's object pooling mechanism that manifests under concurrent async request processing.
Affected products
- Apache Tomcat 11.0.22–11.0.26, 10.1.55–10.1.60, 9.0.118–9.0.122
Timeline
- 2026-10-20: disclosed