Critical Apache Tomcat Flaw Lets Remote Attackers Join Trusted Server Clusters Without Authentication
What happened?
The Apache Software Foundation has disclosed a critical flaw in Apache Tomcat that allows a remote attacker to join a trusted server cluster without authentication. Tracked as CVE-2026-133325, the flaw affects clusters that use TLS 1.3 with a pre-shared key. Apache published the advisory on November 19, 2026, and credited researcher Mike Read with finding the issue. The Apache Tomcat 11 security advisory identifies versions 11.0.28 and 11.0.29 as affected. Apache also lists Tomcat 10.1.62 and 9.0.124. Running one of those versions does not by itself mean a server is exposed.
Key details
- Affected versions include Tomcat 11.0.28, 11.0.29, 10.1.62, and 9.0.124 across respective branches.
- Tomcat failed to verify the identity of the remote server in the affected TLS 1.3 cluster setup.
- Apache recommends switching cluster communication to TLS 1.2 while keeping the pre-shared key enabled.
- Fixed versions are pending release: 11.0.30, 10.1.63, and 9.0.125 for their respective branches.
- No active exploitation or remote code execution from cluster joining is reported in the advisory.
What is affected?
- Apache Tomcat 11.0.28 and 11.0.29
How do I fix or mitigate it?
- Switch cluster communication to TLS 1.2 while keeping pre-shared key enabled.
- Restrict cluster ports to approved servers and review logs for unexpected membership changes.
What should defenders look for?
- Unexpected cluster membership changes in logs.
Summarised by SecOraLens from Cyber Security News. Always read the original source before acting. How SecOraLens verifies advisories.
What to do next
Brief your board. Brief your team.
Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.
