CVE-2026-133325: Apache Tomcat: Cluster TLS-PSK configured to use TLS 1.3 does not validate peer
CVE-2026-133325 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- Critical
- CVSS base score
- 8.1 (Red Hat)
- Weakness
- CWE-322 Key exchange without entity authentication
- Fixed releases
- Apache: 11.0.30, 10.1.63, 9.0.123
- Red Hat: tomcat10-main-10.1.61-0.1.hum1, tomcat11-main-11.0.27-0.1.hum1, RHSA-2026:85926
- Assigned by
- apache (CNA)
- CVE record published
- Listed by VulniPulse
- Record changed
Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-133325; each belongs to its advisory, not to every product listed. How records are collected and checked.
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.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.
Text from the CVE.org record (apache).
How do I fix CVE-2026-133325?
Upgrade to a fixed release named by the vendor:
- Apache: 11.0.30, 10.1.63, 9.0.123
- Red Hat: tomcat10-main-10.1.61-0.1.hum1, tomcat11-main-11.0.27-0.1.hum1, RHSA-2026:85926
- 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. (Apache)
- Restrict network access to Tomcat clustering communication ports so that only authorized cluster nodes can communicate with the cluster receiver. For example, using firewalld: ``` firewall-cmd --permanent --zone=internal --add-source= firewall-cmd --permanent --zone=internal --add-port= /tcp firewall-cmd --reload ``` Alternatively, configure the cluster transport in Tomcat's `server.xml` to utilize TLS 1.2 instead of TLS 1.3 when using TLS-PSK, or replace TLS-PSK with mutual TLS (mTLS) utilizing X.509 certificates. Warning: Altering the Tomcat cluster configuration requires restarting the Tomcat service (`systemctl restart tomcat`), which will cause a temporary interruption of service. (Red Hat)
Vendor advisories for CVE-2026-133325
Apache
1 advisory- Advisory severityCritical
Critical [CVE-2026-133325] 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
CVE-2026-133325Source published Source updated
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.
- Affected products in this advisory
- Apache Tomcat
- Source-reported affected versions
- 11.0.29
- 10.1.62
- 9.0.124
- Source-reported fixed versions
- 11.0.30
- 10.1.63
- 9.0.123
- Mitigation guidance
- 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.
Red Hat
1 advisory- Advisory severityHigh8.1
High [CVE-2026-133325] Unauthorized cluster access via unauthenticated TLS-PSK key exchange
CVE-2026-133325Source published Source updated
Unauthorized cluster access via unauthenticated TLS-PSK key exchange. Red Hat rates this important (CVSS 8.1). Weakness: CWE-322. Red Hat lists fixing advisory RHSA-2026:85926 with package tomcat10-main-10.1.61-0.1.hum1, tomcat11-main-11.0.27-0.1.hum1. Affected product named by the advisory: Red Hat Hardened Images.
- Related products — impact not confirmed
- Red Hat Hardened Images
- Source-reported affected versions
- Affected-version details not available in this record.
- Source-reported fixed versions
- tomcat10-main-10.1.61-0.1.hum1
- tomcat11-main-11.0.27-0.1.hum1
- RHSA-2026:85926
- Mitigation guidance
- Restrict network access to Tomcat clustering communication ports so that only authorized cluster nodes can communicate with the cluster receiver. For example, using firewalld: ``` firewall-cmd --permanent --zone=internal --add-source=<TRUSTED_NODE_IP> firewall-cmd --permanent --zone=internal --add-port=<CLUSTER_PORT>/tcp firewall-cmd --reload ``` Alternatively, configure the cluster transport in Tomcat's `server.xml` to utilize TLS 1.2 instead of TLS 1.3 when using TLS-PSK, or replace TLS-PSK with mutual TLS (mTLS) utilizing X.509 certificates. Warning: Altering the Tomcat cluster configuration requires restarting the Tomcat service (`systemctl restart tomcat`), which will cause a temporary interruption of service.
References
Timeline
- CVE record published
- First vendor advisory listed by VulniPulse
More Apache advisories
CVE-2026-121649Nov 19, 2026Apache Tomcat information disclosureCVE-2026-118436Nov 19, 2026Apache Tomcat denial of serviceCVE-2026-118233Nov 19, 2026Apache Tomcat denial of serviceCVE-2026-118028Nov 19, 2026Execution After Redirect (EAR) vulnerability in Apache Tomcat in RedirectValveCVE-2026-117517Nov 19, 2026Apache Tomcat: The fix for CVE-2026-25854 was incompleteCVE-2026-116830Nov 19, 2026Apache Tomcat denial of service
Get an email when Apache publishes the next one.
See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.