The flaw is limited to a cluster configuration
CVE-2026-133325 is a peer authentication flaw in Apache Tomcat clustering. A cluster that uses TLS 1.3 with a pre-shared key (TLS-PSK) may accept a node without validating its identity. An unauthenticated node could then join the trusted cluster.
A Tomcat version in the affected range does not prove that a server is exposed. The risky condition is the combination of the affected Tomcat version, clustering, TLS-PSK and TLS 1.3. A standard Tomcat web application that does not use this cluster configuration is not affected by this specific path.
Confirm your version and cluster protocol
Apache lists Tomcat 11.0.28 to 11.0.29, 10.1.62 and 9.0.124 as affected. The version alone is not enough to determine exposure. Check whether the cluster is enabled, whether it uses TLS-PSK, and which TLS version the nodes negotiate.
Review the configuration on every node and on any load balancer or proxy that affects cluster traffic. Keep a record of the cluster membership, peer addresses and current protocol settings. Ask the system owner before changing a production cluster.
Use TLS 1.2 until the fixed release is available
Apache recommends switching the affected cluster to TLS 1.2 with TLS-PSK as a temporary mitigation. Apply the change consistently to all cluster members. Test node discovery, replication and failover in a safe environment, then confirm that connections use TLS 1.2 after the production change.
Apache lists Tomcat 11.0.30, 10.1.63 and 9.0.125 as the releases that contain the fix. These were marked not yet released on Apache’s security pages when this article was prepared on 21 November 2026. Check the relevant Tomcat security page for release status before upgrading.
Review cluster membership after mitigation
Check cluster logs and membership records for nodes that your team does not recognise. Preserve relevant logs and the configuration state if you find an unexpected peer. Follow your incident process to determine whether the node could access or change replicated data.
Keep the mitigation in place until you install a fixed release and verify it on every node. Record the installed Tomcat version, negotiated TLS version and a successful cluster health check. CYPEE Cyber can review an approved server and network scope and validate the resulting configuration.
