Live › vulnerability › CVE-2026-101296
Go to dashboardWhen Tomcat's JNDI realm uses a SASL mechanism other than GSSAPI, the authentication step can be skipped. An attacker can log in without the correct password.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| Apache Tomcat 11 | maven | >= 11.0.0-M1, <= 11.0.26 | 11.0.27 |
| Apache Tomcat 10.1 | maven | >= 10.1.0-M1, <= 10.1.60 | 10.1.61 |
| Apache Tomcat 9 | maven | >= 9.0.0.M1, <= 9.0.122 | 9.0.123 |
| Apache Tomcat 8.5 | maven | >= 8.5.0, <= 8.5.100 (EOL) | – |
11.0.27, 10.1.61 or 9.0.123. 8.5.x and 7.0.x are EOL and affected with no fix, so migrateEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A missing critical step in authentication vulnerability in Apache Tomcat when the JNDI realm was configured with with a non GSSAPI SASL authentication mechanism allowed attackers to authenticate without providing the correct password.
This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.26, from 10.1.0-M1 through 10.1.60, from 9.0.0.M1 through 9.0.122.
The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Other unsupported versions may also be affected.
Users are recommended to upgrade to version 11.0.27, 10.1.61 or 9.0.123, which fix the issue.
This page as .md · .json · in your agent: get_signal("CVE-2026-101296")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.