Skip to content
VulniPulse
Advisory severityCritical9.1Apache Software Foundation Updated

Critical [CVE-2026-101296] 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 critical-severity Apache Software Foundation advisory covers CVE-2026-101296 affecting Apache Tomcat.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-101296 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Apache Software FoundationTomcat
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation 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.

Matching phone alertsOptional email delivery

Summary

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.

Affected versions
  • 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
  • 7.0.0 through 7.0.109.
  • through 9.0.122
  • through 7.0.109

Official advisory · high-confidence parse· fetched 24 hours ago·verify at source

Fixed versions
  • 11.0.27
  • 10.1.61
  • 9.0.123

Official advisory · high-confidence parse· fetched 24 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Users are recommended to upgrade to version 11.0.27, 10.1.61 or 9.0.123, which fix the issue.

Official advisory · high-confidence parse· fetched 24 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.