Tomcat CVE-2026-133325: cluster mitigation while fixed releases are pending
Apache rates CVE-2026-133325 Critical and dates its public disclosure to November 19, 2026. Administrators of affected Tomcat clusters should apply Apache’s interim TLS 1.2 guidance to the cluster communication channel while preparing for the fixed release in their branch.
On November 22, Apache still labels all three fixed versions as unreleased. Its download pages offer 9.0.124, 10.1.62 and 11.0.29. A planned version in a security-page heading is not an available upgrade.
Affected versions and planned fixes
| Tomcat branch | Versions listed as affected | Planned fixed version | Release status checked November 22 |
|---|---|---|---|
| 9.0 | 9.0.124 | 9.0.125 | Not yet released |
| 10.1 | 10.1.62 | 10.1.63 | Not yet released |
| 11.0 | 11.0.28 through 11.0.29 | 11.0.30 | Not yet released |
These are Apache’s branch-specific bounds from the Tomcat 9, Tomcat 10 and Tomcat 11 security pages. The advisory concerns cluster communication; the version list alone does not establish that every installation uses the affected feature. For a distribution package or an application that embeds Tomcat, consult its supplier’s CVE status and package revision before deciding whether an upstream version number proves patch status.
Apply the interim guidance to the cluster channel
Inventory the running Tomcat release on every cluster member using its startup version information and deployment records. Record which members communicate with each other and who owns their cluster configuration. A package downloaded to a host is not evidence that its running process uses that version.
Apache recommends TLS 1.2 until the fixed release is available. Apply that mitigation to the affected Tomcat cluster channel, using the configuration procedure for your Tomcat branch or packaged product. Changing client-facing HTTPS settings alone does not implement this cluster mitigation. Do not disable encryption to work around a protocol mismatch.
Plan a coordinated change across the cluster. Confirm protocol compatibility before changing members, preserve the configuration needed for recovery, and arrange a maintenance window if the change can interrupt replication. After applying it, review the effective cluster configuration and ordinary connection logs, then check normal membership and application replication health. These checks confirm operation after maintenance; they are not vulnerability tests.
Move to the fixed release when it is available
Check the official 9.0 downloads, 10.1 downloads or 11.0 downloads together with the matching security page. Once Apache publishes the branch’s fixed release, obtain it through the official distribution channel and follow the published integrity-verification instructions. For vendor packages, use the supplier’s supported update path and explicit CVE fix status.
Test the update with the application’s Java runtime and clustering configuration before rollout. After restarting or replacing each instance, verify the running release, cluster membership and replication health. Keep the interim mitigation in place until the rollout and any subsequent configuration changes have been reviewed. Do not downgrade to an older release solely because it falls outside this CVE’s listed bounds; other security fixes may be lost.
Acknowledgements
This post was created with assistance from AI.