# CVE-2026-101356: Apache Tomcat object recycling vulnerability in HTTP/2 async servlets

Source: https://junglewise.ai/threats/cve-2026-101356-incorrect-object-recycling-and-re-use-vulnerability-in-apache  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-20. Updated: 2026-10-20  
License: CC BY 4.0 with a link back

CVE-2026-101356 · Severity: info · Published 2026-10-20

Apache Tomcat is a web server that powers many corporate applications. A flaw in how it recycles objects during HTTP/2 processing of asynchronous servlets can cause requests and responses to be mixed up between different users, potentially exposing sensitive data or allowing cross-user request tampering.

Technologies: [Apache Tomcat](https://junglewise.ai/threats/technologies/tomcat). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## 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

## References

- [https://lists.apache.org/thread.html/d1xjt7bbjqw7y7n5mcb4fm815hpfgc27](https://lists.apache.org/thread.html/d1xjt7bbjqw7y7n5mcb4fm815hpfgc27)

## Related threats

- [Apache Tomcat Jakarta Security credential handler bypass](https://junglewise.ai/threats/cve-2026-111248-the-jakarta-security-identity-store-backed-by-the-tomcat-user)
- [Apache Tomcat incomplete cleanup in TLS 1.3 connections](https://junglewise.ai/threats/cve-2026-93446-incomplete-cleanup-vulnerability-in-apache-tomcat-could-cause-tls)
- [Apache Tomcat HTTP trailer information leak between requests](https://junglewise.ai/threats/cve-2026-88041-incomplete-cleanup-vulnerability-in-apache-tomcat-allowed-an)
- [Apache Tomcat TOCTOU race condition in APR/Native connector](https://junglewise.ai/threats/cve-2026-80353-time-of-check-time-of-use-toctou-race-condition-vulnerability-in)
- [Apache Tomcat Execution After Redirect vulnerability](https://junglewise.ai/threats/cve-2026-74049-execution-after-redirect-ear-vulnerability-in-apache-tomcat-this)