CVE-2026-101296
9.1CriticalPublished 20 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Impact
- High impact on confidentiality, integrity
- Weakness
- CWE-304
Impact
Unauthenticated attackers with network access can bypass authentication and log in without providing valid passwords. This requires Tomcat to be configured using a JNDI realm with a non-GSSAPI SASL mechanism.
Root cause
A missing critical step in authentication allows authentication to succeed without validating credentials when using non-GSSAPI SASL in JNDI realms.
Affected systems
Apache Tomcat 11.0.0-M1 through 11.0.26, 10.1.0-M1 through 10.1.60, 9.0.0.M1 through 9.0.122, 8.5.0 through 8.5.100 (EOL), and 7.0.0 through 7.0.109 (EOL).
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade to Apache Tomcat 11.0.27, 10.1.61, or 9.0.123. If patching immediately is not possible, disable non-GSSAPI SASL authentication in your JNDI realm configuration.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
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.