Skip to content
Fencer Intel
critical —

CVE-2026-133325 json

Apache Tomcat: Cluster TLS-PSK configured to use TLS 1.3 does not validate peer

published 3h ago modified 2h ago also EUVD-2026-130776

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

Key exchange without entity authentication vulnerability in Apache Tomcat allowed an unauthenticated node to join a cluster when the cluster was secured with TLS 1.3 and TLS-PSK.

This issue affects Apache Tomcat: 11.0.29, 10.1.62, 9.0.124.

Users are recommended to switch to TLS 1.2 and PLDS-PSK or upgrade to version 11.0.30, 10.1.63 or 9.0.123 (when released), which fix the issue.

Is CVE-2026-133325 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-133325 updated cvss 8.1

tomcat: tomcat: Unauthorized cluster access via unauthenticated TLS-PSK key exchange

  • Red Hat Hardened Images tomcat10 10.1.61-0.1.hum1, tomcat11 11.0.27-0.1.hum1
    affected: workaround, no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Affected products

  • Apache Software Foundation Apache Tomcat

Classification

Weakness
  • CWE-322 Key Exchange without Entity Authentication
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.