External risk intelligence

Apache Tomcat Cluster Key Exchange Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-133325

This vulnerability affects Apache Tomcat clustering communication, which is typically configured as an internal, back-end service between server nodes rather than an internet-facing endpoint. While the cluster communication occurs over a network, it is generally kept isolated from the public internet in standard deployment patterns.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Apache Tomcat's clustering feature could allow an unauthorized node to join a cluster when specific security protocols are in use. This could potentially lead to unauthorized access or disruption of services within the cluster.

  • Unauthorized nodes can join secure Tomcat clusters.
  • It impacts internal, back-end communication services.
  • Confirm relevance and exposure to internal clusters.

Attack Path

How an attacker could exploit the issue

An attacker could potentially join a secured Apache Tomcat cluster without proper authentication by exploiting a vulnerability in the key exchange process. This would require the cluster to be configured with TLS 1.3 and TLS-PSK, and the attacker would need network access to the cluster. Successfully joining the cluster could lead to significant compromise of confidentiality, integrity, and availability.

  • Entry condition: Network access to a TLS 1.3/TLS-PSK secured cluster.
  • Trigger point: Vulnerable key exchange in cluster communication.
  • Resulting risk: Unauthenticated cluster node access.

Live Threat

Current exploitation, exposure, and threat context

In Apache Tomcat clusters secured with TLS 1.3 and TLS-PSK, an unauthenticated node could join the cluster. This occurs because the key exchange process lacks entity authentication, allowing unauthorized nodes to participate in cluster communications when supported by the advisory.

  • Cluster node authentication.
  • Unauthenticated node joins cluster.
  • Unauthorized cluster access.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Apache Tomcat affects the clustering mechanism when secured with TLS 1.3 and TLS-PSK. Infrastructure and platform teams responsible for Tomcat deployments should prioritize identifying all instances of the affected software. Confirming reachability and business criticality will inform the risk-based prioritization for remediation.

  • Infrastructure or platform teams own the issue.
  • Verify TLS 1.3 and TLS-PSK cluster configurations.
  • Plan remediation based on identified exposure.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Apache Tomcat?

Apache Tomcat is a widely used open-source web server and servlet container that runs Java code. It is often employed to host enterprise web applications and facilitates communication between different server nodes when configured as a cluster.

What does CVE-2026-133325 mean?

This CVE describes a weakness in how Tomcat handles key exchanges, classified as CWE-322 (Key Exchange without Entity Authentication). It means the server fails to properly verify the identity of a node trying to connect, allowing an unauthorized system to join a secure cluster.

How can an attacker trigger this vulnerability?

An attacker needs network access to the cluster's communication channel and must target a system configured specifically with TLS 1.3 and TLS-PSK. If the cluster uses different protocols, such as TLS 1.2, or is not set up for clustering, this specific trigger path is not present.

Is my server at risk if it is not internet-facing?

Halo Surface Signal indicates this vulnerability is unlikely to affect internet-facing endpoints because it targets back-end clustering traffic. While usually isolated, you should still evaluate if your internal network architecture allows unauthorized segments to reach these cluster ports.

Do I need to update my Apache Tomcat installation?

If you use clustering, check if you are running the affected versions (11.0.29, 10.1.62, or 9.0.124). If you are using TLS 1.3 with TLS-PSK, consider switching to TLS 1.2 with PLDS-PSK as a temporary measure until you can upgrade to the patched versions.

References