High [CVE-2026-101296] Authentication bypass via non-GSSAPI SASL in JNDI realm
This high-severity Red Hat Linux advisory covers CVE-2026-101296; related products: Red Hat Hardened Images.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
Authentication bypass via non-GSSAPI SASL in JNDI realm. Red Hat rates this important (CVSS 7.4).
Weakness: CWE-303. Red Hat lists fixing advisory RHSA-2026:85926 with package tomcat10-main-10.1.61-0.1.hum1, tomcat11-main-11.0.27-0.1.hum1.
Affected product named by the advisory: Red Hat Hardened Images.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 13 hours ago·verify at source
- tomcat10-main-10.1.61-0.1.hum1
- tomcat11-main-11.0.27-0.1.hum1
- RHSA-2026:85926
Official advisory · high-confidence parse· fetched 13 hours ago·verify at source
Mitigation checklist
- --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. 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. These controls limit blast radius and contain exploitation, but they do not fix the underlying missing critical authentication step defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-201 Zero Trust Gateway / Identity-Aware Proxy (medium)
Official advisory · high-confidence parse· fetched 13 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.