Skip to content
VulniPulse
Advisory severityHigh7.3Apache Software Foundation

High [CVE-2026-75973] Improper Authentication vulnerability in Apache Tomcat

This high-severity Apache Software Foundation advisory covers CVE-2026-75973 affecting Apache Tomcat.

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

CVE-2026-75973 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 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Improper Authentication vulnerability in Apache Tomcat. When Jakarta Authentication was configured with SimpleAuthConfigProvider as the default provider and multiple web application used that provider, the realm for the first web application to authenticate a request would be used for all web applications.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.25, from 10.1.0-M1 through 10.1.59, from 9.0.0.M4 through 9.0.121.

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.

Other unsupported versions may also be affected.

Users are recommended to upgrade to version 11.0.26, 10.1.60, 9.0.122, which fixes the issue.

Affected versions
  • 11.0.0-M1 through 11.0.25
  • 10.1.0-M1 through 10.1.59
  • 9.0.0.M4 through 9.0.121.
  • 8.5.0 through 8.5.100.
  • through 9.0.121
  • through 8.5.100

Official advisory · high-confidence parse· fetched 13 days ago·verify at source

Fixed versions
  • 11.0.26
  • 10.1.60
  • 9.0.122

Official advisory · high-confidence parse· fetched 13 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Users are recommended to upgrade to version 11.0.26, 10.1.60, 9.0.122, which fixes the issue.

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