Quick answers
- Is CVE-2026-101296 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101296 being exploited in the wild.
- How severe is CVE-2026-101296?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Apache Tomcat 9.0.0-M1 through 9.0.122, 10.1.0-M1 through 10.1.60, 11.0.0-M1 through 11.0.26; also 8.5.0–8.5.100 and 7.0.0–7.0.109 (EOL).
- Is there a fix for CVE-2026-101296?
- 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-101296 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-101296?
- 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
The vulnerability is an authentication bypass in Tomcat's JNDI realm implementation when using non-GSSAPI SASL authentication mechanisms. A missing validation step allows attackers to authenticate without providing valid credentials. The issue affects supported versions 11.0.0-M1 through 11.0.26, 10.1.0-M1 through 10.1.60, and 9.0.0-M1 through 9.0.122, as well as out-of-support versions 8.5.0–8.5.100 and 7.0.0–7.0.109.
Affected products
- Apache Tomcat 9.0.0-M1 through 9.0.122, 10.1.0-M1 through 10.1.60, 11.0.0-M1 through 11.0.26; also 8.5.0–8.5.100 and 7.0.0–7.0.109 (EOL)
Timeline
- 2026-10-20: disclosed