CVE-2026-55957: Apache Tomcat has a Missing Critical Step in Authentication vulnerability

Published Jun 29, 2026
·
Updated

Missing Critical Step in Authentication vulnerability in Apache Tomcat when the JNDIRealm was configured to authenticate binds using GSSAPI allowed attackers to authenticate without provided the correct password.

This issue affects Apache Tomcat: from 11.0.0 through 11.0.4, from 10.1.0 through 10.1.36, from 9.0.0 through 9.0.100, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109.

Users are recommended to upgrade to version 11.0.5, 10.1.37 or 9.0.101, which fixes the issue.

Other sources

Missing Critical Step in Authentication vulnerability in Apache Tomcat when the JNDIRealm was configured to authenticate binds using GSSAPI allowed attackers to authenticate without provided the correct password.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.4, from 10.1.0-M1 through 10.1.36, from 9.0.0.M1 through 9.0.100, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109.

Users are recommended to upgrade to version 11.0.5, 10.1.37 or 9.0.101, which fixes the issue.

— MITRE

Missing Critical Step in Authentication vulnerability in Apache Tomcat when the JNDIRealm was configured to authenticate binds using GSSAPI allowed attackers to authenticate without providing the correct password.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.4, from 10.1.0-M1 through 10.1.36, from 9.0.0.M1 through 9.0.100, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109.

Users are recommended to upgrade to version 11.0.5, 10.1.37 or 9.0.101, which fixes the issue.

— OSV

Affected Software

22 affected componentsFixes available
Apache Tomcat>=11.0.0-M1<=11.0.4, >=10.1.0-M1<=10.1.36, >=9.0.0.M1<=9.0.100, >=8.5.0<=8.5.100, >=7.0.0<=7.0.109
Apache Tomcat<9.0.101
Apache Tomcat>=10.1.0<10.1.37
Apache Tomcat>=11.0.0<11.0.5
maven/org.apache.tomcat.embed:tomcat-embed-core>=11.0.0-M1<11.0.5
11.0.5
maven/org.apache.tomcat.embed:tomcat-embed-core>=10.1.0-M1<10.1.37
10.1.37
maven/org.apache.tomcat.embed:tomcat-embed-core>=9.0.0.M1<9.0.101
9.0.101
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.5.0<=8.5.100
maven/org.apache.tomcat.embed:tomcat-embed-core<=7.0.109
maven/org.apache.tomcat:tomcat>=11.0.0-M1<11.0.5
11.0.5
maven/org.apache.tomcat:tomcat>=10.1.0-M1<10.1.37
10.1.37
maven/org.apache.tomcat:tomcat>=9.0.0.M1<9.0.101
9.0.101
maven/org.apache.tomcat:tomcat>=8.5.0<=8.5.100
maven/org.apache.tomcat:tomcat<=7.0.109
maven/org.apache.tomcat:tomcat-catalina>=11.0.0-M1<11.0.5
11.0.5
maven/org.apache.tomcat:tomcat-catalina>=10.1.0-M1<10.1.37
10.1.37
maven/org.apache.tomcat:tomcat-catalina>=9.0.0.M1<9.0.101
9.0.101
maven/org.apache.tomcat:tomcat-catalina>=8.5.0<=8.5.100
maven/org.apache.tomcat:tomcat-catalina<=7.0.109
bitnami/tomcat<9.0.101
9.0.101
bitnami/tomcat>=10.0.0<10.1.37
10.1.37
bitnami/tomcat>=11.0.0<11.0.5
11.0.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 11.0.5
  2. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 10.1.37
  3. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 9.0.101
  4. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.5
  5. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.37
  6. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.101
  7. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 11.0.5
  8. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 10.1.37
  9. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-catalina to a version that resolves this vulnerability.

    Fixed in 9.0.101
  10. Upgrade

    Upgrade bitnami/tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.101
  11. Upgrade

    Upgrade bitnami/tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.37
  12. Upgrade

    Upgrade bitnami/tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.5
  13. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.5
  14. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.37
  15. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.101

Event History

Jun 29, 2026
CVE Published
via MITRE·08:47 PM
Data Sourced
via MITRE·08:47 PM
DescriptionWeakness
Data Sourced
via OSV·08:47 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·09:02 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via OSV·09:32 PM
Data Sourced
via OSV·09:32 PM
Affected Software
Aug 7, 2026
Exploit Published
via GitHub·08:02 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-55957?

The severity of CVE-2026-55957 is rated at 76 on the risk scale, indicating a significant security concern.

2

How do I fix CVE-2026-55957?

To fix CVE-2026-55957, upgrade Apache Tomcat to version 11.0.5 or later, or 10.1.5 or later.

3

What versions of Apache Tomcat are affected by CVE-2026-55957?

CVE-2026-55957 affects Apache Tomcat versions from 11.0.0-M1 through 11.0.4 and from 10.1.0-M1 through 10.1.4.

4

What is the nature of the vulnerability in CVE-2026-55957?

CVE-2026-55957 is an authentication bypass vulnerability that allows attackers to authenticate without providing the correct password.

5

What is JNDIRealm in relation to CVE-2026-55957?

JNDIRealm is a component in Apache Tomcat that interacts with a Java Naming and Directory Interface, and in this vulnerability, it allowed improper authentication when configured with GSSAPI.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203