Tomcat cluster flaw lets unauthenticated hosts join (CVE-2026-133325)
Only TLS 1.3 pre-shared-key clusters are exposed; fixed builds 11.0.30, 10.1.63, and 9.0.125 are still pending.
Unauthenticated cluster join in Apache Tomcat (TLS 1.3 TLS-PSK)
Apache Tomcat has a key-exchange flaw that omits entity authentication. An unauthenticated remote node can join a cluster when that cluster is secured with TLS 1.3 and TLS-PSK. Joining lets the node participate in the trusted cluster. Affected releases are Tomcat 11.0.29, 10.1.62, and 9.0.124.
What to do: Switch cluster security to TLS 1.2 and PLDS-PSK, or upgrade to 11.0.30, 10.1.63, or 9.0.123 when released.
| Product | Affected | Fixed in |
|---|---|---|
| Apache Tomcat | 11.0.29, 10.1.62, 9.0.124 | 11.0.30, 10.1.63, 9.0.123 (when released) |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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.
Only TLS 1.3 pre-shared-key clusters are exposed; fixed builds 11.0.30, 10.1.63, and 9.0.125 are still pending.
CVE-2026-133325 hits Tomcat 11.0.28–11.0.29, 10.1.62 and 9.0.124; fixes are 11.0.30, 10.1.63 and 9.0.125.
The Cyber Centre says Tomcat 11.0.29, 10.1.62, and 9.0.124 and earlier are affected and updates should be applied when available.
Today 838 readers · 918 views · 88 reads · all time 215K views