The Apache Software Foundation disclosed a critical peer authentication bypass in Apache Tomcat that allows an unauthenticated node to join a cluster secured with TLS 1.3 and a pre-shared key (PSK).
Tracked as CVE-2026-133325, the defect affects Tomcat 11.0.28 through 11.0.29, 10.1.62, and 9.0.124. Exposure depends on both the deployed release and the cluster transport configuration: an affected version alone does not establish that a deployment uses the affected TLS 1.3 and PSK configuration.
The defect is classified as CWE-322, key exchange without entity authentication. In the affected configuration, the cluster transport can establish an encrypted connection without validating that the connecting endpoint is an authorized peer.
Critical Apache Tomcat Security Flaw
Encryption protects traffic in transit; peer authentication determines whether the endpoint should be trusted to participate. This failure occurs at the boundary between cluster members, unlike the Tomcat JNDIRealm authentication bypass, which involved credential validation for directory-backed application authentication.
A successful encrypted handshake therefore does not, by itself, demonstrate that the cluster has authenticated the remote node. Administrators should assess the inter-node transport separately from public HTTPS listeners and TLS termination at reverse proxies or load balancers.
A front-end listener that enforces TLS 1.3 says nothing about authentication on the backend cluster channel. The distinction also separates this disclosure from the WebSocket endpoint security-constraint bypass, which involved request-path parsing and application access controls.
Apache identifies unauthorized cluster membership as the impact of CVE-2026-133325; the disclosure does not establish remote code execution or confirm that production clusters have been compromised.
Apache recommends temporarily configuring affected clusters to negotiate TLS 1.2 while retaining PSK authentication. That workaround changes the cluster protocol without removing the shared credential.
Reverting to the deprecated EncryptInterceptor is not equivalent: Apache recommends migrating away from it, and the separate EncryptInterceptor protection bypass illustrates why the older mechanism is not a substitute.
After applying the workaround, operators should verify the protocol actually negotiated between peers, particularly where deployment templates and runtime settings may differ across cluster members.
The corrective releases are Tomcat 11.0.30, 10.1.63, and 9.0.125 for their respective branches. The CVE description contains an inconsistent 9.x upgrade reference, but Apache’s Tomcat 9 security page identifies 9.0.125 as the corrective release and lists it as not yet released.
Inventory the running version on every member, including instances launched from older container images or deployment templates. Keep TLS 1.2 with PSK in place until each affected member runs a corrected build; updating only the public-facing tier does not correct backend cluster transport.
During remediation, restrict access to the cluster transport to approved peers and compare observed membership with the expected node inventory.
Investigate unexpected member additions or connections from unapproved addresses, but do not treat either observation alone as proof of exploitation.
Network restrictions reduce exposure but don’t fix the underlying authentication failure. Before restoring TLS 1.3, verify the running version on every affected node and confirm that legitimate members can communicate normally after the upgrade.
Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team

