CVE-2026-133325: Apache Tomcat: Cluster TLS-PSK configured to use TLS 1.3 does not validate peer
Exploitation: None known · CVSS 9.8 Critical · Unauthenticated · Published 2026-11-19
Description
Key exchange without entity authentication vulnerability in Apache Tomcat allowed an unauthenticated node to join a cluster when the cluster was secured with TLS 1.3 and TLS-PSK. This issue affects Apache Tomcat: 11.0.28-11.0.29, 10.1.62, 9.0.124. Users are recommended to switch to TLS 1.2 and TLS-PSK or upgrade to version 11.0.30, 10.1.63 or 9.0.125 (when released), which fix the issue.
Enclave's analysis
Tomcat's clustering layer can be told to protect node-to-node replication traffic with a shared key (TLS-PSK). If that's paired with TLS 1.3, Tomcat skips validating the peer, so any node that doesn't know the key can still join the cluster and read or tamper with replicated session data. Clustering and TLS-PSK are both off by default and have to be deliberately turned on, and an attacker needs network access to the replication port to try it. No PoC, exploit code or in-the-wild activity has surfaced; drop to TLS 1.2 now or patch to the fixed release.
Fix
No fixed version in the CVE record yet. Follow the vendor advisory.
Affected versions
| Product | Vulnerable | Fixed in |
|---|---|---|
| Apache Tomcat | 11.0.28 through 11.0.29 | Not listed |
| Apache Tomcat | 10.1.62 | Not listed |
| Apache Tomcat | 9.0.124 | Not listed |
| Embedded Tomcat Maven artifacts (org.apache.tomcat:tomcat-catalina, org.apache.tomcat.embed:*) bundled inside apps such as Spring Boot | Same version ranges as standalone Tomcat (9.0.124; 10.1.62; 11.0.28-11.0.29), but only if the embedding app also enables clustering with TLS-PSK/TLS 1.3 — not verifiable from dependency data alone | Not listed |