CVE-2026-133325
Apache Tomcat: Cluster TLS-PSK configured to use TLS 1.3 does not validate peer
No exploitation reported by the sources we read.
- Published2026-11-19
- WeaknessCWE-322
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2026-11-1921:38CVE publishedCNA
Versions per branch
Products declared by the CNA1 product
As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Apache Software Foundation Apache Tomcatother versions: not affectedAffected
- ≥ 11.0.28, ≤ 11.0.29no fix statedsemver
- = 10.1.62no fix statedsemver
- = 9.0.124no fix statedsemver
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-19
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- tomcat10Debian:14all versions · no fixed version listedand 1 other package
- tomcat10Debian:13all versions · no fixed version listedand 1 other package
- tomcat10Debian:12all versions · no fixed version listed
- tomcat9Debian:14all versions · fixed in 9.0.70-2
- tomcat9Debian:13all versions · fixed in 9.0.70-2
- tomcat9Debian:12all versions · fixed in 9.0.70-2
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-20
- Metasploit modules
- none listed Metasploit Framework
Sources
Identifiers
- EUVD-2026-130776same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-j322-r8cv-7j54same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-11-19
- Last Modified
- 2026-11-20
- NVD status
- Awaiting Analysis
- GitHub Advisory
- GHSA-j322-r8cv-7j54
Frequently asked questions
What is CVE-2026-133325?
Is CVE-2026-133325 actively exploited?
What is the CVSS score for CVE-2026-133325?
Running tomcat9? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-j322-r8cv-7j54
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OpenCVE · OpenCVE terms of service · terms restrict redistribution
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- CISA Vulnrichment · CC0-1.0