Critical Apache Tomcat Flaw Allows Unauthorized Cluster Membership via TLS 1.3 Weakness
A critical vulnerability in Apache Tomcat, CVE-2026-133325, permits unauthenticated remote attackers to join trusted server clusters by exploiting a weakness in TLS 1.3 configurations using pre-shared keys.

The Apache Software Foundation has disclosed a critical flaw in its widely-used Apache Tomcat server software, identified as CVE-2026-133325. This vulnerability allows remote attackers to join a trusted server cluster without requiring any form of authentication, posing a significant risk to environments relying on clustered Tomcat instances for session replication and load balancing.
The flaw specifically affects Tomcat versions 11.0.28 through 11.0.29, 10.1.62, and 9.0.124. Crucially, the vulnerability is only present in clusters configured to use TLS 1.3 with a pre-shared key (PSK) for inter-node communication. In such configurations, Tomcat fails to properly verify the identity of other members attempting to join the cluster, allowing an attacker with network access to the cluster communication port to establish a connection and become a recognized member.
Apache's advisory, released on November 19, 2026, credits researcher Mike Read for discovering the issue. While the vulnerability does not lead to remote code execution (RCE) on its own, gaining unauthorized access to a cluster can have severe implications. Attackers could potentially intercept sensitive session data, disrupt cluster operations, or use the compromised node as a pivot point for further network intrusion.
The Apache Tribes component, responsible for communication between servers in a Tomcat cluster, is where the failure occurs. When using TLS 1.3 with a PSK, the expected identity verification step is bypassed, meaning encrypted communication can be established without confirming the legitimacy of the connecting server. This contrasts with older vulnerabilities that might have targeted different encryption mechanisms within Tomcat.
As a temporary workaround, Apache recommends that administrators reconfigure their cluster communication to use TLS 1.2 while keeping the pre-shared key enabled. This change applies specifically to the traffic between Tomcat servers, not to the HTTPS connections used by end-users accessing web applications hosted on the servers. Administrators are urged to implement this workaround promptly.
Apache is preparing to release patched versions of Tomcat to address the vulnerability. These include versions 11.0.30, 10.1.63, and 9.0.125 for the respective branches. Users should monitor for these updates and plan for their deployment as soon as they become available.
Beyond applying the workaround or updating the software, security best practices for managing Tomcat clusters include restricting network access to cluster communication ports to only authorized servers and regularly reviewing logs for any signs of unexpected membership changes or suspicious activity. Verifying that all expected cluster members reconnect successfully after applying changes is also a critical step.
It is important to note that this vulnerability, CVE-2026-133325, is distinct from other previously disclosed Apache Tomcat flaws, such as CVE-2026-34486, which involved an exploited encryption flaw. While both relate to security within Tomcat, they represent different attack vectors and should be tracked and remediated independently.