---
title: Tip: if your Tomcat cluster uses TLS-PSK, pin it to TLS 1.2 now; don't fall back to the deprecated EncryptInterceptor | ctxsec
url: https://ctxsec.com/items/tip-tomcat-cluster-tls-psk-pin-tls-1-2-until-11-0-30-10-1-63-9-0-125-and-retire-encryptinterceptor
description: "CVE-2026-133325 lets an unauthenticated node join a Tomcat cluster secured with TLS-PSK over TLS 1.3, and the fixed releases are not out yet. Tomcat's interim advice is TLS 1.2. The older EncryptInterceptor has its own unfixed flaws (CVE-2026-95517), so it isn't a safe alternative."
status: "guide (based on Apache Tomcat security pages, Nov 19, 2026)"
published: 2026-11-20
---

> CVE-2026-133325 lets an unauthenticated node join a Tomcat cluster secured with TLS-PSK over TLS 1.3, and the fixed releases are not out yet. Tomcat's interim advice is TLS 1.2. The older EncryptInterceptor has its own unfixed flaws (CVE-2026-95517), so it isn't a safe alternative.

[← Tips & Guides](/tips) · [markdown](/items/tip-tomcat-cluster-tls-psk-pin-tls-1-2-until-11-0-30-10-1-63-9-0-125-and-retire-encryptinterceptor.md)

guide (based on Apache Tomcat security pages, Nov 19, 2026)

2026-11-20 11:44 AM ET

### Tip: if your Tomcat cluster uses TLS-PSK, pin it to TLS 1.2 now; don't fall back to the deprecated EncryptInterceptor

- **Find clusters:** search `server.xml` for `<Cluster` elements and TLS-PSK settings on the cluster receiver/sender.
- **Pin** the cluster TLS protocol to TLS 1.2 and restart nodes one at a time.
- **Isolate** cluster membership and replication ports to a dedicated network or VLAN regardless.

Sources: [Apache Tomcat 11.x security page: CVE-2026-133325 (Critical, made public Nov 19, 2026)](https://tomcat.apache.org/security-11.html) · [Apache Tomcat 10.x security page: CVE-2026-133325](https://tomcat.apache.org/security-10.html)
