CyberSecurityNews

Critical Apache Tomcat Flaw Lets Remote Attackers Join Trusted Server Clusters Without Authentication


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.

The flaw requires the affected cluster encryption setup, and a remote attacker needs network access to the service that handles communication between cluster members. A public Tomcat website does not necessarily expose that service.

Apache Tomcat branchAffected versionsPatched version (pending release)
11.0.x11.0.28–11.0.2911.0.30
10.1.x10.1.6210.1.63
9.0.x9.0.1249.0.125

Tomcat Cluster Authentication Failed

Apache Tribes handles communication between servers in a Tomcat cluster. Those servers can share session data so that a user can stay signed in when another server takes over. A pre-shared key is a secret configured on trusted members in advance.

In the affected TLS 1.3 setup, Tomcat did not verify the identity of the server at the other end of the connection. The connection could be encrypted without proving that the server was allowed to join.

Cyber Security News previously covered flaws in Tomcat’s EncryptInterceptor, an older component used to protect cluster traffic. The new advisory concerns a different failure: Tomcat accepted a cluster member it had not authenticated. Apache’s advisory does not report active exploitation or say that joining a cluster gives an attacker remote code execution.

Apache recommends switching cluster communication to TLS 1.2 while keeping the pre-shared key enabled. This change applies to traffic between Tomcat servers, not the HTTPS connections used by website visitors. The fixed versions are 11.0.30, 10.1.63, and 9.0.125 for their respective branches. Apache listed them as pending release in its Tomcat 11, Tomcat 10, and Tomcat 9 security notices.

Administrators should check the running version and cluster settings on every member, restrict cluster ports to approved servers, and review available logs for unexpected membership changes. After applying the workaround or updating, confirm that every expected member reconnects and that session replication still works where enabled. A website can still respond while its servers are no longer sharing session data.

The earlier CISA warning about an exploited Tomcat encryption flaw concerned CVE-2026-34486. That warning does not establish exploitation of CVE-2026-133325, and the two flaws should be tracked separately.



Source link