CVE-2026-133325 Tomcat flaw lets attackers join clusters

Apache Tomcat has a critical authentication flaw that lets an unauthenticated attacker join a trusted server cluster, provided the cluster uses TLS 1.3 with a pre-shared key. The flaw, tracked as CVE-2026-133325, was disclosed by the Apache Software Foundation on 19 November 2026, and researcher Mike Read is credited with finding it. No exploitation has been confirmed so far, and the patched releases are still pending.
The danger is not to every Tomcat website. It is specific to clustered deployments that encrypt traffic between their own servers in one particular way. A normal public Tomcat site that does not run a cluster, or that does not use this exact cluster encryption setup, is not exposed by this flaw.
What the flaw does
Tomcat clusters use a component called Apache Tribes to let several server instances talk to each other and share session data, so a user can stay signed in when another server takes over. A pre-shared key is a secret configured in advance on the trusted members of the cluster.
In the affected setup, Tomcat encrypts the connection between cluster members but does not check the identity of the server at the other end. As Cyber Security News reports, the connection could be encrypted without proving that the server was allowed to join. An attacker with network access to the service that handles communication between cluster members could therefore present itself as a trusted node.
Once inside the cluster, a rogue node could read shared traffic and session data, and potentially inject bad data into it. Because cluster nodes share live session state, that could include user sessions. Apache's advisory does not say that joining a cluster gives an attacker remote code execution, and that should not be assumed.
Which versions are affected
The flaw affects three recent builds across the supported Tomcat lines, according to the Apache Tomcat 11 security advisory: Tomcat 11.0.28 and 11.0.29, Tomcat 10.1.62, and Tomcat 9.0.124. Only clusters configured with TLS 1.3 and TLS-PSK are affected. The CVSS score for the flaw was still awaiting analysis at the time of reporting.
The fixed versions are 11.0.30 for the 11.0 line, 10.1.63 for the 10.1 line, and 9.0.125 for the 9.0 line. Apache listed those releases as pending at the time the advisory was published, so administrators should watch for them rather than assume they are already available to download.
What to do now
Apache recommends switching cluster communication to TLS 1.2 while keeping the pre-shared key enabled, as an interim step until the fixed builds ship. That change applies to traffic between Tomcat servers, not to the HTTPS connections used by website visitors, so it should not change how the public site behaves.
Administrators should check the running version and the cluster settings on every member of each cluster, and restrict the cluster communication ports so only approved servers can reach them. Logs should be reviewed for unexpected membership changes, since a rogue node joining would be the first sign of trouble.
After applying the workaround or updating, confirm that every expected member reconnects and that session replication still works where it is enabled. A website can still respond normally while its servers are no longer sharing session data, so a working homepage is not proof the cluster is healthy.
What this flaw is not
This is a different flaw from an earlier Tomcat issue, CVE-2026-34486, which was the subject of a CISA warning about an exploited Tomcat encryption flaw. That warning does not establish exploitation of CVE-2026-133325, and the two flaws should be tracked separately. There is also no confirmed public exploit code for CVE-2026-133325 at present.
The narrow scope is genuinely good news for most Tomcat users, but it is no reason for clustered deployments to wait. The fix is a version upgrade, the workaround is a configuration change, and the window between disclosure and patch availability is exactly when attackers study advisories. Clustered Tomcat operators should apply the TLS 1.2 workaround now and plan the upgrade for the day the fixed releases land.
Sources: Cyber Security News and SecurityOnline.info.