Apache says the cluster does not validate a peer in this configuration, allowing an unauthenticated node to join. The issue concerns cluster membership, not every Tomcat web application or every TLS connection.Apache rates the issue Critical and identifies affected releases in the 11.0, 10.1 and 9.0 branches. The risk depends on both the installed version and the cluster encryption settings. Operators should check both before treating a Tomcat server as exposed.
What it allows
How Does CVE-2026-133325 Affect Cluster Authentication?
Apache identifies a key exchange that lacks entity authentication when a Tomcat cluster uses TLS 1.3 with TLS-PSK. In that configuration, an unauthenticated node can join the cluster. Apache does not describe an application-level entry point or a confirmed downstream data impact in its advisory.
Cluster operators should treat unexpected membership as a security signal and review access to the cluster network. This is our defensive reading of Apache’s stated impact, not a published detection signature. A Vulnerability Intelligence platform can help organize the affected release and configuration checks.
What Is Known About Exploitation?
The CISA KEV catalog version dated 20 November 2026 does not list CVE-2026-133325. Brandefense Blackhole counted one dark-chat post matching this CVE from 23 August through 21 November 2026. That count measures a discussion signal, not an incident or confirmed exploitation.
Who is affected
Version Check
| Release Line | Affected Range | Fixed In |
|---|---|---|
| 11.x | 11.0.28 to before 11.0.30 | 11.0.30 |
| 10.x | 10.1.62 to before 10.1.63 | 10.1.63 |
| 9.x | 9.0.124 to before 9.0.125 | 9.0.125 |
For distribution packages and custom builds, check the supplier’s advisory.
Only clusters using TLS 1.3 with TLS-PSK are exposed. The corrected upstream releases are not yet published; check downstream backports with the package vendor.
Which Tomcat Versions and Settings Are Affected?
Apache lists Tomcat 11.0.28 through 11.0.29, 10.1.62 and 9.0.124 as affected. The condition is a cluster secured with TLS 1.3 and TLS-PSK. A version match without that configuration does not establish exposure to this cluster flaw.
Apache names 11.0.30, 10.1.63 and 9.0.125 as the intended corrected releases, but marks them not yet released on its branch security pages. An earlier 9.x number must not be treated as a fix for affected 9.0.124. Document each node’s running version and effective cluster TLS configuration in the vulnerability management process.
Check the installed build on every cluster node, including nodes supplied through a distribution package. Apache’s upstream version list does not establish whether a downstream package contains a backported fix. Record package vendor guidance separately before closing remediation.
Timeline
- 2026-11-16
Apache says the issue was reported to its Tomcat security team.
- 2026-11-19
Apache published its Critical advisory and CVE-2026-133325.
- 2026-11-20
CISA KEV catalog version 2026.11.20 did not list the CVE.
What to do
-
Inventory cluster nodes and TLS settings
Identify every Tomcat cluster node, its running release, and whether cluster encryption combines TLS 1.3 with TLS-PSK. Prioritize matching deployments on the listed affected versions.
-
Apply Apache’s temporary mitigation
Switch affected cluster encryption to TLS 1.2 with TLS-PSK while the corrected upstream releases remain unavailable. Validate that every node uses the intended protocol after the change.
-
Plan the branch update
When Apache publishes them, update affected 11.0.x, 10.1.x, and 9.0.x branches to 11.0.30, 10.1.63, and 9.0.125 respectively, or a later corrected release.
-
Verify the running deployment
After updating, check which Tomcat installation each running node uses. For upstream installs, run CATALINA_HOME/bin/version.sh (or version.bat on Windows) and verify its build after restarting the service. For distribution packages, verify the package build and backport status with the vendor. Review cluster membership for unfamiliar peers. Keep the patch management record tied to the verified build.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-133325 in Brandefense Atlas
The Atlas record of CVE-2026-133325: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-133325 affect every Tomcat deployment?
No. Apache describes the issue for clusters using TLS 1.3 with TLS-PSK on the listed releases. Verify the running version and cluster settings.
Which Tomcat versions are listed as affected?
Apache lists 11.0.28 through 11.0.29, 10.1.62, and 9.0.124. The relevant cluster must also use TLS 1.3 with TLS-PSK.
What should administrators do before corrected releases arrive?
Apache recommends switching affected clusters to TLS 1.2 with TLS-PSK. Confirm the effective protocol on every node after the change.
Are the named corrected releases already available?
Apache’s branch security pages mark 11.0.30, 10.1.63, and 9.0.125 as not yet released. Check the official release status before planning an upgrade.
Sources
- Apache Tomcat CVE-2026-133325 Security AdvisoryApache Software Foundation
- Apache Tomcat 11.x VulnerabilitiesApache Software Foundation
- Apache Tomcat 10.x VulnerabilitiesApache Software Foundation
- Apache Tomcat 9.x VulnerabilitiesApache Software Foundation
- Apache Tomcat 11 Security ConsiderationsApache Software Foundation
- CVE-2026-133325 RecordApache CNA via CVE Program
- CISA Known Exploited Vulnerabilities CatalogCISA