BIT-tomcat-2026-101296: Apache Tomcat: JNDIRealm bind credential validation fails open for non-GSSAPI SASL mechanisms
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 through 11.0.26, from 10.1.0 through 10.1.60, from 9.0.0 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
bitnami/tomcatto a version that resolves this vulnerability.Fixed in 9.0.123 - Upgrade
Upgrade
bitnami/tomcatto a version that resolves this vulnerability.Fixed in 10.1.61 - Upgrade
Upgrade
bitnami/tomcatto a version that resolves this vulnerability.Fixed in 11.0.27 - Upgrade
Upgrade
Apache Tomcatto a version that resolves this vulnerability.Fixed in 11.0.27 - Upgrade
Upgrade
Apache Tomcatto a version that resolves this vulnerability.Fixed in 10.1.61 - Upgrade
Upgrade
Apache Tomcatto a version that resolves this vulnerability.Fixed in 9.0.123
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments are affected when Apache Tomcat uses the JNDI realm configured with a non-GSSAPI SASL authentication mechanism. Tomcat installations not using that realm configuration are not identified as affected by the provided information.
What does an attacker need to exploit the vulnerability?
An attacker can authenticate without supplying the correct password when the affected JNDI realm configuration is in use. No privileges or user interaction are indicated by the supplied severity vector.
Are default Tomcat deployments affected?
The issue depends on configuring the JNDI realm with a non-GSSAPI SASL mechanism. The provided information does not state that this is enabled by default.
What versions should be used to remediate the issue?
Upgrade to Apache Tomcat 11.0.27, 10.1.61, or 9.0.123. Affected supported ranges are 11.0.0 through 11.0.26, 10.1.0 through 10.1.60, and 9.0.0 through 9.0.122; listed EOL ranges are also known to be affected.
How can I determine whether my deployment needs immediate remediation?
Check both the Tomcat version and realm configuration. Immediate remediation is needed if the deployment is within an affected range and its JNDI realm uses a non-GSSAPI SASL authentication mechanism.