Skip to content
TrustList
Security advisories

Apache Tomcat clusters on TLS-PSK and TLS 1.3 let unauthenticated nodes join

Editorial

By TrustList Editorial

A critical Tomcat flaw lets an unauthenticated node join a cluster secured with TLS 1.3 and TLS-PSK; the fixed 9.0.125, 10.1.63 and 11.0.30 are not yet released, so the project advises TLS 1.2 for now.

About Apache Tomcat clusters on TLS-PSK and TLS 1.3 let unauthenticated nodes join

Apache Tomcat clusters on TLS-PSK and TLS 1.3 let unauthenticated nodes join

19 November 2026: The Apache Tomcat security team has published a critical flaw, CVE-2026-133325, in Tomcat's session clustering. When a cluster is secured with TLS 1.3 and a pre-shared key (TLS-PSK), Tomcat does not check who the other node is, so an unauthenticated node can join the cluster. The fixes are in Tomcat 9.0.125, 10.1.63 and 11.0.30, but none of those releases was out when we checked on 22 November. Until they are, the project tells users to switch the cluster to TLS 1.2.

Not yet independently verified. The flaw, affected versions, fixed versions and dates come from the Apache Tomcat security pages for 9.x, 10.x and 11.x, read on 22 November 2026. When we read them, all three fixed releases were still listed as not yet released, and the project had published no CVSS score. We will update this when it can be confirmed, and remove this note.

Only the newest releases, after the EncryptInterceptor move

The Tomcat pages describe the bug as a key exchange without entity authentication. It only matters for clusters that replicate sessions between Tomcat nodes and use TLS-PSK on TLS 1.3. The affected releases are recent ones:

  • Tomcat 11: 11.0.28 and 11.0.29, fixed in 11.0.30;
  • Tomcat 10.1: 10.1.62, fixed in 10.1.63;
  • Tomcat 9: 9.0.124, fixed in 9.0.125.

The narrow range has a cause. TLS-PSK is the replacement Tomcat recommends for the older EncryptInterceptor, which the project deprecated after several flaws found in September. Teams that followed that advice and moved their cluster traffic to TLS-PSK on the newest releases are the ones now exposed.

The issue was reported to the Tomcat security team on 16 November 2026 and made public on 19 November. The fix is already committed to each branch, but no build has been released.

A rogue node can read replicated sessions

A node that joins a Tomcat cluster receives the session data the other nodes replicate, and can send session updates back. In a cluster that holds logged-in user sessions, that can mean reading or changing other users' sessions. The project rates the issue Critical and gives no CVSS score.

Clusters still on the EncryptInterceptor are not a safe place to stay either: the same pages say several of its known problems have not been addressed and that all its users should move to TLS encryption.

Steps for teams running Tomcat clusters

  • Check whether any cluster uses TLS-PSK with TLS 1.3, on 9.0.124, 10.1.62, 11.0.28 or 11.0.29.
  • If it does, switch the cluster connection to TLS 1.2 now, as the project advises.
  • Keep cluster traffic on a private network segment that untrusted hosts cannot reach, so no outside node can try to join.
  • Watch the Tomcat download pages for 9.0.125, 10.1.63 and 11.0.30, and plan the upgrade as soon as they are released.
  • Teams still on the EncryptInterceptor should plan the move to TLS-PSK with TLS 1.2 now, rather than wait.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in