<Vulnerability name="CVE-2026-101296">
    <DocumentDistribution xml:lang="en">Copyright © 2012 Red Hat, Inc. All rights reserved.</DocumentDistribution>
    <ThreatSeverity>Important</ThreatSeverity>
    <PublicDate>2026-10-20T13:45:39</PublicDate>
    <Bugzilla id="2556187" url="https://bugzilla.redhat.com/show_bug.cgi?id=2556187" xml:lang="en:us">
tomcat: tomcat: Authentication bypass via non-GSSAPI SASL in JNDI realm
    </Bugzilla>
    <CVSS3 status="verified">
        <CVSS3BaseScore>7.4</CVSS3BaseScore>
        <CVSS3ScoringVector>CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N</CVSS3ScoringVector>
    </CVSS3>
    <CWE>CWE-303</CWE>
    <Details xml:lang="en:us" source="Mitre">
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.
    </Details>
    <Details xml:lang="en:us" source="Red Hat">
A flaw was found in Apache Tomcat. When the Java Naming and Directory Interface (JNDI) realm is configured with a non-Generic Security Service Application Program Interface (GSSAPI) Simple Authentication and Security Layer (SASL) mechanism, a missing verification step allows an attacker to bypass authentication without providing the correct password. An unauthenticated remote attacker can exploit this vulnerability to gain unauthorized access to protected resources.
    </Details>
    <Statement xml:lang="en:us">
A flaw was found in Apache Tomcat. When the JNDIRealm is configured with a non-GSSAPI SASL authentication mechanism, a missing verification step allows an unauthenticated remote attacker to bypass authentication without supplying valid credentials. Successful exploitation grants unauthorized access to protected web applications and administrative resources hosted on the Tomcat instance, restricted by the operating context and system privileges of the Tomcat process.
    </Statement>
    <Mitigation xml:lang="en:us">
The highest-value action is to reconfigure Tomcat JNDIRealm to enforce Kerberos GSSAPI authentication and eliminate non-GSSAPI SASL authentication mechanisms: upgrade to Apache Tomcat 11.0.27, 10.1.61, or 9.0.123 (or the fixed Tomcat builds), which verify credentials properly during non-GSSAPI SASL authentication in JNDIRealm, closing unauthenticated request to protected realm using non-GSSAPI SASL credentials. Until patched, this is a concern on Tomcat deployments with JNDIRealm configured with a non-GSSAPI SASL authentication mechanism, so restrict network access to endpoints protected by the JNDI realm and avoid using non-GSSAPI SASL authentication configurations. As a compensating measure, intercept and authenticate inbound requests at an identity-aware gateway before they reach the vulnerable Tomcat JNDI realm.
    </Mitigation>
    <AffectedRelease cpe="cpe:/a:redhat:hummingbird:1">
        <ProductName>Red Hat Hardened Images</ProductName>
        <ReleaseDate>2026-10-12T00:00:00Z</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2026:81365">RHSA-2026:81365</Advisory>
        <Package name="tomcat11-main">tomcat11-main-11.0.27-0.1.hum1</Package>
    </AffectedRelease>
    <AffectedRelease cpe="cpe:/a:redhat:hummingbird:1">
        <ProductName>Red Hat Hardened Images</ProductName>
        <ReleaseDate>2026-10-20T00:00:00Z</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2026:85926">RHSA-2026:85926</Advisory>
        <Package name="tomcat10-main">tomcat10-main-10.1.61-0.1.hum1</Package>
    </AffectedRelease>
    <PackageState cpe="cpe:/a:redhat:enterprise_linux:10">
        <ProductName>Red Hat Enterprise Linux 10</ProductName>
        <FixState>Affected</FixState>
        <PackageName>tomcat</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:enterprise_linux:10">
        <ProductName>Red Hat Enterprise Linux 10</ProductName>
        <FixState>Affected</FixState>
        <PackageName>tomcat9</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/o:redhat:rhel_els:6">
        <ProductName>Red Hat Enterprise Linux 6</ProductName>
        <FixState>Affected</FixState>
        <PackageName>tomcat6</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/o:redhat:rhel_els:7">
        <ProductName>Red Hat Enterprise Linux 7</ProductName>
        <FixState>Affected</FixState>
        <PackageName>tomcat</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:enterprise_linux:8">
        <ProductName>Red Hat Enterprise Linux 8</ProductName>
        <FixState>Affected</FixState>
        <PackageName>pki-deps:10.6/pki-servlet-engine</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:enterprise_linux:8">
        <ProductName>Red Hat Enterprise Linux 8</ProductName>
        <FixState>Affected</FixState>
        <PackageName>tomcat</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:enterprise_linux:9">
        <ProductName>Red Hat Enterprise Linux 9</ProductName>
        <FixState>Affected</FixState>
        <PackageName>pki-servlet-engine</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:enterprise_linux:9">
        <ProductName>Red Hat Enterprise Linux 9</ProductName>
        <FixState>Affected</FixState>
        <PackageName>tomcat</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:hummingbird:1">
        <ProductName>Red Hat Hardened Images</ProductName>
        <FixState>Not affected</FixState>
        <PackageName>hi/tomcat</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:jboss_enterprise_web_server:5">
        <ProductName>Red Hat JBoss Web Server 5</ProductName>
        <FixState>Not affected</FixState>
        <PackageName>jws5-tomcat</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:jboss_enterprise_web_server:6">
        <ProductName>Red Hat JBoss Web Server 6</ProductName>
        <FixState>Affected</FixState>
        <PackageName>jws6-tomcat</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:jboss_enterprise_web_server:7">
        <ProductName>Red Hat JBoss Web Server 7</ProductName>
        <FixState>Affected</FixState>
        <PackageName>jws7-tomcat</PackageName>
    </PackageState>
    <References xml:lang="en:us">
https://www.cve.org/CVERecord?id=CVE-2026-101296
https://nvd.nist.gov/vuln/detail/CVE-2026-101296
https://lists.apache.org/thread.html/bl52b9go9ckoov8x4v3dt6rkm573cygd
    </References>
</Vulnerability>