Mozilla's November advisories cover Firefox 160, ESR 153.7, ESR 115.45 and Thunderbird 160 and 153.7; 57 of the 99 Firefox 160 entries are rated high and none is reported as exploited.
Apache Tomcat clusters on TLS-PSK and TLS 1.3 let unauthenticated nodes join
EditorialBy TrustList Editorial
A critical Tomcat flaw lets an unauthenticated node join a cluster secured with TLS 1.3 and TLS-PSK; the fixed 9.0.125, 10.1.63 and 11.0.30 are not yet released, so the project advises TLS 1.2 for now.
- United States of America
- Cybersecurity
- Vulnerability Management
- Patch Management
- +1 more
About Apache Tomcat clusters on TLS-PSK and TLS 1.3 let unauthenticated nodes join
Apache Tomcat clusters on TLS-PSK and TLS 1.3 let unauthenticated nodes join
19 November 2026: The Apache Tomcat security team has published a critical flaw, CVE-2026-133325, in Tomcat's session clustering. When a cluster is secured with TLS 1.3 and a pre-shared key (TLS-PSK), Tomcat does not check who the other node is, so an unauthenticated node can join the cluster. The fixes are in Tomcat 9.0.125, 10.1.63 and 11.0.30, but none of those releases was out when we checked on 22 November. Until they are, the project tells users to switch the cluster to TLS 1.2.
Not yet independently verified. The flaw, affected versions, fixed versions and dates come from the Apache Tomcat security pages for 9.x, 10.x and 11.x, read on 22 November 2026. When we read them, all three fixed releases were still listed as not yet released, and the project had published no CVSS score. We will update this when it can be confirmed, and remove this note.
Only the newest releases, after the EncryptInterceptor move
The Tomcat pages describe the bug as a key exchange without entity authentication. It only matters for clusters that replicate sessions between Tomcat nodes and use TLS-PSK on TLS 1.3. The affected releases are recent ones:
- Tomcat 11: 11.0.28 and 11.0.29, fixed in 11.0.30;
- Tomcat 10.1: 10.1.62, fixed in 10.1.63;
- Tomcat 9: 9.0.124, fixed in 9.0.125.
The narrow range has a cause. TLS-PSK is the replacement Tomcat recommends for the older EncryptInterceptor, which the project deprecated after several flaws found in September. Teams that followed that advice and moved their cluster traffic to TLS-PSK on the newest releases are the ones now exposed.
The issue was reported to the Tomcat security team on 16 November 2026 and made public on 19 November. The fix is already committed to each branch, but no build has been released.
A rogue node can read replicated sessions
A node that joins a Tomcat cluster receives the session data the other nodes replicate, and can send session updates back. In a cluster that holds logged-in user sessions, that can mean reading or changing other users' sessions. The project rates the issue Critical and gives no CVSS score.
Clusters still on the EncryptInterceptor are not a safe place to stay either: the same pages say several of its known problems have not been addressed and that all its users should move to TLS encryption.
Steps for teams running Tomcat clusters
- Check whether any cluster uses TLS-PSK with TLS 1.3, on 9.0.124, 10.1.62, 11.0.28 or 11.0.29.
- If it does, switch the cluster connection to TLS 1.2 now, as the project advises.
- Keep cluster traffic on a private network segment that untrusted hosts cannot reach, so no outside node can try to join.
- Watch the Tomcat download pages for 9.0.125, 10.1.63 and 11.0.30, and plan the upgrade as soon as they are released.
- Teams still on the EncryptInterceptor should plan the move to TLS-PSK with TLS 1.2 now, rather than wait.
Sources
- Apache Tomcat 10.x security page, 19 November 2026
- Apache Tomcat 11.x security page, 19 November 2026
- Apache Tomcat 9.x security page, 19 November 2026
Categories & features
- United States of America
- Cybersecurity
- Vulnerability Management
- Patch Management
- Web Security
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
Seven are rated high, including an account takeover through OAuth2 auto-linking and fork workflows that receive repository secrets. Every release up to 28.2.0 is affected; there is no backport line.
SA-CONTRIB-2026-254 rates CVE-2026-118539 highly critical (21 of 25): no login needed, every configuration exposed and attacks already under way. The security team tells shops to audit their orders.
Google moved Stable and Extended Stable to 156.0.8078.79/.80 with 21 security fixes. One external researcher reported four of them, including the critical one; Google states no exploitation.
Oracle scores the Java gap 9.1 and pulls the eMudhra roots from every supported JDK line; Cisco lists Duo upgrades now, Meraki camera firmware on 18 November and IOS XR 26.4.1 on 30 November.
Releases 26.12.1, 24.22.1 and 22.23.4 close ten CVEs, four rated High, and also drop trust in the compromised eMudhra intermediates through the bundled CA store.
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 close CVE-2026-109618 and CVE-2026-109619. Every PHP install serving web requests is at risk, mod_php most of all, and PHP 8.1 and older get no official fix.
Two flaws rated Important hit all three supported lines, a third affects only Tomcat 11, and the fixed releases have been out since 12 October.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More United States of AmericaThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.