Skip to navigation

Threat reportVulnerabilityTL-2026-6589

Apache Tomcat Tribes Cluster TLS 1.3 PSK Server Identity Not Verified Lets Remote Attackers Join Clusters (CVE-2026-133325)

criticalMONITORING

A key-exchange-without-entity-authentication flaw in Apache Tomcat's Tribes clustering lets an unauthenticated remote node join a cluster secured with TLS 1.3 and TLS-PSK, because the peer is not validated. Apache rates it Critical and published it on 2026-11-19; fixed releases (11.0.30, 10.1.63, 9.0.125) were not yet available at disclosure and no active exploitation or remote code execution has been reported.

Key facts

IdentifiersTL-2026-6589, CVE-2026-133325, CVE-2026-34486
SeverityCRITICAL
CVSS9.8
First disclosed
Exploitation statusLinked CVE exploited in the wild; Listed in CISA KEV: CVE-2026-34486 (added )
EPSSCVE-2026-34486: 42.6% (98.5th percentile); CVE-2026-133325: 0.1% (7.7th percentile)
Affected productsApache Software Foundation Apache Tomcat 11.x; Apache Software Foundation Apache Tomcat 10.1.x; Apache Software Foundation Apache Tomcat 9.0.x
Weaknesses (CWE)CWE-322
MITRE ATT&CK techniquesT1040 Network Sniffing, T1046 Network Service Discovery, T1190 Exploit Public-Facing Application, T1210 Exploitation of Remote Services, T1557 Adversary-in-the-Middle, T1565.002 Data Manipulation: Transmitted Data Manipulation
MotivationUNKNOWN
Target sectorstechnology, finance, government administration, health, telecoms
Target regionsGlobal
Detection rules9 (1 shown free)
Sources11 cited sources

Detection coverage

As of 2026-11-21, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6589 across Splunk SPL, Microsoft KQL and Sigma, covering 14 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Non-Member Peer Connecting To Tomcat Tribes Receiver TCP/4000 (CVE-2026-133325) [Splunk SPL] — Exploitation

Detects a host that is not a registered cluster member establishing a connection to the Apache Tomcat Tribes receiver (TCP/4000 by default). CVE-2026-133325 (CWE-322) means a Tribes channel using TLS-PSK with TLS 1.3 (pskProtocol=TLSv1.3, the default) on Tomcat 11.0.28-11.0.29, 10.1.62 or 9.0.124 does not authenticate the peer, so any host that can reach the receiver may join the cluster. Behaviour-first: it needs only firewall telemetry and a cluster-member allowlist.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1190, T1557
  • Data sources: pan:traffic, CommonSecurityLog, firewall
  • Severity: high
  • Confidence: high

Splunk SPL

index=network sourcetype="pan:traffic" dest_port=4000 action=allowed ```CVE-2026-133325 Tribes receiver TCP/4000 reached by a non-member```
| lookup tomcat_cluster_members ip AS dest_ip OUTPUT cluster_name
| where isnotnull(cluster_name)
| lookup tomcat_cluster_members ip AS src_ip OUTPUT ip AS member_src
| where isnull(member_src)
| stats count earliest(_time) AS first_seen latest(_time) AS last_seen values(dest_ip) AS cluster_nodes by src_ip, dest_port
| convert ctime(first_seen) ctime(last_seen)

Microsoft KQL

let ClusterMembers = dynamic(["10.0.0.11", "10.0.0.12", "10.0.0.13"]);
CommonSecurityLog
| where TimeGenerated > ago(24h)
| where DestinationPort == 4000 and DeviceAction in~ ("allow", "allowed", "accept")
| where DestinationIP in (ClusterMembers) and SourceIP !in (ClusterMembers)
| summarize Connections = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort
| project SourceIP, DestinationIP, DestinationPort, Connections, FirstSeen, LastSeen

Sigma

title: Non-Member Peer Connecting To Tomcat Tribes Receiver TCP/4000 (CVE-2026-133325)
id: 6f1c2a54-3b8e-4d71-9a40-1e2c7b6d8a01
status: experimental
description: Detects a non-member host connecting to the Apache Tomcat Tribes receiver on TCP/4000. CVE-2026-133325 lets an unauthenticated peer join a TLS-PSK TLS 1.3 cluster on Tomcat 11.0.28-11.0.29, 10.1.62 and 9.0.124.
references:
  - https://tomcat.apache.org/security-11.html
  - https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-133325
  - https://github.com/apache/tomcat/commit/2e6c85ba0937f3dc9877dadd433167fcd45f8dbc
  - https://tomcat.apache.org/tomcat-11.0-doc/config/cluster-channel.html
author: Threadlinqs Team
date: 2026-11-20
tags:
  - attack.initial-access
  - attack.credential-access
  - attack.collection
  - attack.t1190
  - attack.t1557
  - cve.2026-133325
logsource:
  category: firewall
detection:
  selection:
    dst_port: 4000
    action: allowed
  filter_cluster_members:
    src_ip|cidr:
      - '10.0.0.0/28'
  condition: selection and not filter_cluster_members
falsepositives:
  - New cluster node added but not yet in the allowlist
  - Authorised vulnerability scanner
level: high

Known false positives:

  • Newly deployed cluster node not yet in the member allowlist
  • Authorised vulnerability scanner or load-test host reaching TCP/4000

Tuning notes: Populate the tomcat_cluster_members lookup (columns ip, cluster_name) and the KQL ClusterMembers list / Sigma cidr filter with real member addresses. Change 4000 if the Tribes receiver port is customised. Swap pan:traffic for your firewall or Zeek conn sourcetype. Only clusters on TLS-PSK with TLS 1.3 are vulnerable, so alert severity can be lowered for clusters already on pskProtocol=TLSv1.2.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple and Gold in full, 2 calls a day on a free account)
  • Tomcat JVM Accepting Tribes Connection From Non-Member Host (CVE-2026-133325) [Sentinel KQL] — Exploitation · unlock with TL Creds
  • Tomcat Node Requesting Session State From Unknown Peer (CVE-2026-133325) [Sentinel KQL] — Post-Exploitation · unlock with TL Creds
  • Tomcat JVM Connecting Out To Non-Member On Tribes Port 4000 (CVE-2026-133325) [Sentinel KQL] — C2 / Lateral Movement · unlock with TL Creds
  • Vulnerable Apache Tomcat Release Running (CVE-2026-133325 Exposure) [Sigma] — Exploitation Exposure · unlock with TL Creds
  • Large Data Transfer Between Tomcat Cluster And Non-Member On Tribes Port (CVE-2026-133325) [Sigma] — Post-Exploitation · unlock with TL Creds
  • Tomcat server.xml Cluster Configuration Modified (CVE-2026-133325 Exposure Change) [Sigma] — Configuration Tampering · unlock with TL Creds
  • Unknown Node Added To Tomcat Tribes Cluster Membership (CVE-2026-133325) [Splunk SPL] — Post-Exploitation · unlock with TL Creds
  • Multi-Host Probing Of Tomcat Tribes Port TCP/4000 (CVE-2026-133325 Reconnaissance) [Splunk SPL] — C2 / Lateral Movement · unlock with TL Creds

Indicators of compromise

As of 2026-11-21, Threadlinqs Intelligence tracks 14 indicators of compromise for TL-2026-6589.

Sample indicators (3 of 14)

  • URL: hxxps://lists[.]apache[.]org/thread.html/b53dmjwf81667pw1r27zxx8s6hw71bdn
  • File hash: 2e6c85ba0937f3dc9877dadd433167fcd45f8dbc
  • File hash: 8dcddccc600c2cc315e649df2244bdc902e8801e

Defanged, TLP:CLEAR. Full set of 14 indicators: unlock with TL Creds.

14 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

CVE-2026-133325 (Apache title: "Cluster TLS-PSK configured to use TLS 1.3 does not validate peer") concerns cluster TLS-PSK in Apache Tomcat. Apache's own entry does not name the component; Cyber Security News and Tomcat's cluster-channel documentation place it in the Tribes group-communication layer that Tomcat uses for clustering and session replication. Tomcat's cluster Channel supports TLS pre-shared-key (TLS-PSK) protection, enabled by setting pskIdentity and pskKey and selecting pskProtocol (TLSv1.2 or TLSv1.3, default TLSv1.3). When the channel is configured with TLS 1.3 and TLS-PSK, Tomcat does not verify the identity of the peer at the other end of the connection. Apache describes the weakness as a key exchange without entity authentication that allowed an unauthenticated node to join a cluster. NVD maps it to CWE-322 (Key Exchange without Entity Authentication).

Exploitation requires network access to the cluster member communication service (the Tribes receiver, TCP/4000 by default per third-party reporting) on a deployment that has enabled TLS-PSK with TLS 1.3. No credentials or knowledge of the PSK are described as necessary. Apache's advisory and the NVD record do not describe the impact beyond cluster membership; neither reports remote code execution or active exploitation. A node that is accepted into a cluster could, depending on configuration, take part in cluster messaging and session replication, but that downstream impact is an inference, not a sourced finding.

Affected versions per Apache: Tomcat 11.0.28 to 11.0.29, 10.1.62 and 9.0.124. Fixes are committed (11.x 2e6c85ba0937f3dc9877dadd433167fcd45f8dbc, 10.1.x 8dcddccc600c2cc315e649df2244bdc902e8801e, 9.0.x 8dac862e720a9b2ce681ee160e87666aba796192) and will ship in 11.0.30, 10.1.63 and 9.0.125, which were not yet released at publication. The NVD description lists 9.0.123 as the 9.x fixed version, which conflicts with 9.0.124 being affected; Apache's page (9.0.125) is treated as authoritative. The documented workaround is to switch the cluster to TLS 1.2 until the fixed release is available. The issue was reported to the Tomcat security team on 2026-11-16 and made public on 2026-11-19. Cyber Security News credits researcher 'Mike Read'; Apache's pages do not name a reporter, so this credit is unconfirmed.

This is distinct from CVE-2026-34486, a CISA KEV-listed EncryptInterceptor bypass (a regression of the CVE-2026-29146 fix; CVSS 3.1 7.5) in the same Tribes component. Exploitation of CVE-2026-34486 does not establish exploitation of CVE-2026-133325. Apache's entry for CVE-2026-95517 also tells users to be mindful of CVE-2026-133325 and use only TLS 1.2 until the fix ships. Apache documents EncryptInterceptor as deprecated, so some operators may have moved to TLS-PSK, which puts them in scope here. As of 2026-11-19 NVD lists the record as Received with no CVSS score; severity here follows Apache's Critical rating.

MITRE ATT&CK techniques by tactic:

Credential Access

T1040 Network Sniffing; T1557 Adversary-in-the-Middle

Discovery

T1046 Network Service Discovery

Initial Access

T1190 Exploit Public-Facing Application

Lateral Movement

T1210 Exploitation of Remote Services

Collection

T1557 Adversary-in-the-Middle

Impact

T1565.002 Data Manipulation: Transmitted Data Manipulation

Remediation

Patches

  • Upgrade to Tomcat 11.0.30, 10.1.63 or 9.0.125 when released (not yet available at disclosure)

Immediate actions

  • Identify Tomcat clusters that use Tribes TLS-PSK with pskProtocol=TLSv1.3 (the default) on 11.0.28-11.0.29, 10.1.62 or 9.0.124
  • Switch the cluster channel to pskProtocol=TLSv1.2 until the fixed release is available (Apache-recommended workaround)
  • Restrict network access to the Tribes receiver port (TCP/4000 by default) to known cluster members using firewall or segmentation rules

Workarounds

  • Use TLS 1.2 for cluster TLS-PSK communication instead of TLS 1.3

Longer-term hardening

  • Keep cluster traffic on an isolated, non-routable management network
  • Monitor cluster membership changes and unexpected peers connecting to the Tribes receiver
  • Review use of the deprecated EncryptInterceptor and patch CVE-2026-34486 (KEV-listed) separately

Affected and fixed versions

  • Apache Software Foundation — Apache Tomcat 11.x
    Vulnerable versions: 11.0.28; 11.0.29
    Fixed in: 11.0.30 (not yet released at disclosure)
  • Apache Software Foundation — Apache Tomcat 10.1.x
    Vulnerable versions: 10.1.62
    Fixed in: 10.1.63 (not yet released at disclosure)
  • Apache Software Foundation — Apache Tomcat 9.0.x
    Vulnerable versions: 9.0.124
    Fixed in: 9.0.125 (not yet released at disclosure; NVD text says 9.0.123)

Timeline

Last updated · revalidated 1× · latest source

  • Related, separate flaw CVE-2026-34486 (EncryptInterceptor bypass in Tomcat Tribes) reported to the Tomcat security team.
  • CVE-2026-34486 made public by Apache; fixed in Tomcat 11.0.21, 10.1.54 and 9.0.117.
  • Per HeroDevs, CISA added CVE-2026-34486 to the Known Exploited Vulnerabilities catalog. This is a separate CVE and does not imply exploitation of CVE-2026-133325.
  • Tomcat 11.0.29 / 10.1.62 / 9.0.124 release series (security-page headings dated 2026-11-13 and 2026-11-16); these exact versions were later listed as vulnerable to CVE-2026-133325.
  • CVE-2026-133325 reported to the Apache Tomcat security team.
  • NVD published CVE-2026-133325 at 22:18 UTC (status Received, CWE-322 from security@apache.org, no CVSS metrics); description text mentions 9.0.123 as fixed, conflicting with Apache's 9.0.125.
  • Apache published the advisory (rated Critical) for 11.0.28-11.0.29, 10.1.62 and 9.0.124, with fix commits but no released fixed version; NVD record created (status Received, CWE-322, no CVSS).
  • Apache CNA updated the CVE record; workaround wording (switch to TLS 1.2 with TLS-PSK) present in the MITRE record.
  • Cyber Security News reported the flaw and recommended TLS 1.2 as the workaround; no exploitation reported.
  • NVD record modified with CISA ADP enrichment: CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); SSVC Exploitation none, Automatable yes, Technical Impact total. GBHackers coverage notes no confirmed compromise.

Update history

Sources cited

Other reports on CVE-2026-34486

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 11 sources; published ; last updated .

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats