Apache Tomcat: Cluster TLS-PSK configured to use TLS 1.3 does not validate peer
Get instant alerts when new vulnerabilities affect Apache Tomcat - before attackers find them.
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.29, 10.1.62, 9.0.124. Users are recommended to switch to TLS 1.2 and PLDS-PSK or upgrade to version 11.0.30, 10.1.63 or 9.0.123 (when released), which fix the issue.
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
Generated by AI (claude-fable-5.1) and published by VulnTracker. It is not reviewed by a person, so check the vendor advisory before you act on it.
If your Tomcat cluster uses TLS 1.3 with TLS-PSK, switch it to TLS 1.2 with TLS-PSK or restrict the cluster ports now. Then move to Apache's fixed releases (11.0.30, 10.1.63, 9.0.125) once available, or, on Red Hat Hardened Images, apply RHSA-2026:85926 / RHSA-2026:81365.
A fix is recorded
Guidance updated 2026-11-20
Sign in free to see the steps, fixed versions and workarounds.
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
Get alerted
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
This product uses data from the NVD API but is not endorsed or certified by the NVD. CVE records are from the CVE Program (CVE.org).