Skip to main content
CVE-2026-133325VulnerabilityPublished

tomcat · Key Exchange Without Entity Authentication Vulnerability

Affects tomcatSource GCVE Database

0
Compare
Authoritative record:CVE-2026-133325· High

Not known to be exploited.

Data as of 20 Nov 2026, 01:38 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.apache.tomcat/tomcatpkg:maven/org.apache.tomcat/tomcatOther threatsAffected
  • =11.0.29
  • =10.1.62
  • =9.0.124
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade affected Apache Tomcat versions to 11.0.30, 10.1.63, or 9.0.123 (upon release) to fix the vulnerability. Alternatively, switching the cluster security configuration to use TLS 1.2 with PLDS-PSK is recommended as a temporary mitigation.

Description

A vulnerability in Apache Tomcat's cluster key exchange mechanism allows an unauthenticated node to join a cluster when using TLS 1.3 with TLS-PSK. This affects versions 9.0.124, 10.1.62, and 11.0.29. The issue is resolved by upgrading to versions 9.0.123 (when released), 10.1.63, or 11.0.30, or by switching to TLS 1.2 with PLDS-PSK.

References

Community reviews

Loading reviews…