CVE-2026-133325 can leave a cluster with a peer that the operator did not intend to admit. The fix and the temporary TLS 1.2 mitigation prevent new vulnerable handshakes when applied correctly. Incident response also needs a way to find evidence from the period before remediation.

Vulnerability overview

Apache published CVE-2026-133325 for a Critical cluster authentication flaw. An unauthenticated node can join a Tomcat cluster when TLS 1.3 and TLS-PSK protect cluster communication. The issue is CWE-322 and appears in the GitHub Advisory Database with CVSS 3.1 9.8.

Tomcat 11.0.28 and 11.0.29, Tomcat 10.1.62, and Tomcat 9.0.124 are affected. Apache identifies 11.0.30, 10.1.63, and 9.0.125 as fixed releases. Until installation, the vendor recommends switching cluster encryption to TLS 1.2 with TLS-PSK.

Mechanism and exploitation conditions

TLS 1.3 allows a peer to ignore the PSK and use a certificate-authenticated handshake. The Tomcat cluster channel did not verify that the PSK was used, and certificate verification was not configured for that trust path. The result was acceptance of a peer that had not satisfied the expected PSK check.

The fix checks for peer certificates after the handshake and rejects the connection when one is present. A TLS 1.3 PSK handshake has no peer certificate, so this test distinguishes the intended state from the fallback.

An incident candidate requires a vulnerable cluster, TLS 1.3, TLS-PSK, and network access to the secure listener. Investigators should also consider an internal node that was already compromised. Cluster access may come from the same trusted network that legitimate applications use.

Impact

Cluster membership can expose replication traffic and influence coordination among nodes. The exact consequences vary with the cluster manager, application sessions, and message types. Analysts should describe observed membership and data flows rather than assume that every accepted peer achieved application takeover.

The reviewed sources do not confirm exploitation in the wild. That means a positive finding in local logs would be important evidence, not a routine expected event.

Affected products and scope

Inventory the affected version and the secure cluster topology. Include node addresses, receiver ports, static Member entries, firewall rules, and certificate paths used by TLS nodes. A cluster may have several interfaces, and only one may expose the secure transport.

Retain logs from the period when TLS 1.3 was active. Cluster startup and membership logs, TLS handshake errors, firewall or flow records, container configuration history, and deployment records may each answer a different question. Do not change the cluster key before deciding whether logs or packet metadata need preservation.

Exposure context

On 21 November 2026, ZoomEye Search for app="Apache Tomcat" returned 591661 matches. The CVE Filter returned 0. Exposure uses 591661 and is a product-fingerprint count, not a confirmed vulnerable asset count.

The result can guide external inventory reconciliation. It cannot show cluster membership or whether a suspicious peer connected. Network flow data and Tomcat cluster logs are the relevant evidence sources for that question.

Remediation and mitigations

Immediately restrict secure cluster ports to approved members. Change cluster encryption to TLS 1.2 with TLS-PSK if the fixed release cannot be installed at once. Upgrade to 11.0.30, 10.1.63, or 9.0.125, then test the certificate-only rejection path in a controlled cluster.

A response checklist should cover the following:

  • Compare observed member addresses with the approved static Member list.

  • Look for new or short-lived peers around the disclosure window.

  • Review session replication and application access logs for unusual state use.

  • Preserve configuration snapshots and relevant network flow records.

  • Rotate the PSK after containment and evidence collection decisions.

  • Validate that every node rejects a certificate-only peer.

Assign the investigation to the cluster owner and involve application and network teams for data and flow interpretation. Close the ticket only after the fixed build is confirmed on every node and the negative authentication test succeeds.

References

  • Apache advisory: https://lists.apache.org/thread/b53dmjwf81667pw1r27zxx8s6hw71bdn

  • Tomcat cluster security guidance: https://tomcat.apache.org/tomcat-11.0-doc/cluster-howto.html

  • Tomcat 11 security page: https://tomcat.apache.org/security-11.html

  • Tomcat 10 security page: https://tomcat.apache.org/security-10

  • Tomcat 9 security page: https://tomcat.apache.org/security-9

  • Fix commit and regression test: https://github.com/apache/tomcat/commit/2e6c85ba0937f3dc9877dadd433167fcd45f8dbc

  • GitHub advisory: https://github.com/advisories/GHSA-j322-r8cv-7j54