Skip to content
VulniPulse
Advisory severityCritical9.8Apache Software Foundation

Critical [CVE-2026-76183] Apache Tomcat: Bypass of security constraints for WebSocket endpoints

This critical-severity Apache Software Foundation advisory covers CVE-2026-76183 affecting Apache Tomcat.

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

CVE-2026-76183 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

Authentication Bypass by Alternate Name vulnerability in Apache Tomcat allowed the security constraints for any WebSocket endpoint to be bypassed.

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.M1 through 9.0.121.

The following versions were EOS at the time the CVE was created but are known to be affected: from 8.5.0 through 8.5.100, from 7.0.43 through 7.0.109.

Other unsupported versions may also be affected.

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

Affected versions
  • Apache Tomcat 11.0.0-M1 through 11.0.25
  • Apache Tomcat 10.1.0-M1 through 10.1.59
  • Apache Tomcat 9.0.0.M1 through 9.0.121
  • Apache Tomcat 8.5.0 through 8.5.100
  • Apache Tomcat 7.0.43 through 7.0.109

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 or 9.0.122, which fix 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.