Skip to content

ApplicationsCritical 9.8Patch available

CVE-2026-133325

Auth bypass in Tomcat cluster allows unauthenticated node join via TLS 1.3 + PSK

How scary is it?

updated 21 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • Yes

    Proof-of-concept code is public2

    1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list3

    Not in the catalog as of our last sync.

Scare-o-meter

Act this week

Serious and within reach of attackers. Schedule the fix this week.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: Reachable over the network with no login and no user action; CVSS 9.8.1 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run Apache Software Foundation Apache Tomcat in an affected version>= 11.0.28 and <= 11.0.29 / 10.1.62 / 9.0.124

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

  2. Recommendation, AI-writtenUpgrade to 11.0.30/10.1.63/9.0.125 or revert cluster to TLS1.2+PSK until fixed

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Reachable over the network with no login and no user action; CVSS 9.8.

CVSS
9.8Criticalscored by CISA
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
0.57%chance of exploitation in the next 30 daystop 52% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
19 Nov 2026analysed here 21 Nov 2026

Summary

Impact

Unauthenticated attacker can join a Tomcat cluster (via TLS1.3+PSK), enabling session theft, data exposure, lateral movement, or possible remote code actions in clustered apps.

Triage

Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
No. See why

Executive summary (AI-written)

CVE-2026-133325 is a critical vulnerability affecting multiple versions of Apache Tomcat that could allow unauthenticated attackers to join Tomcat clusters, posing a severe risk to sensitive data and overall application integrity. With a CVSS score of 9.8, this vulnerability enables attackers to potentially engage in session theft, data exposure, lateral movement within the network, or even remote execution in clustered applications. Given the widespread use of Tomcat in various industries, the business impact could be substantial, ranging from reputational damage to legal ramifications resulting from data breaches.

Technical analysis (AI-written)

CVE-2026-133325 presents a major security flaw in Apache Tomcat versions 11.0.28, 11.0.29, 10.1.62, and 9.0.124, concerning an authentication bypass during the node joining process in Tomcat clusters using TLS 1.3 with Pre-Shared Key (PSK). An unauthenticated attacker could exploit this vulnerability to join a Tomcat cluster, allowing unauthorized access to cluster resources and communications. By exploiting this weakness, attackers could engage in session hijacking and steal sensitive data or execute arbitrary remote commands within the application cluster, thus compromising both application integrity and confidentiality. The potential for lateral movement within the network represents a severe escalation of risk following the initial intrusion.

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.

Affected products

ProductAffected versions
Apache Software Foundation Apache Tomcat>= 11.0.28 and <= 11.0.2910.1.629.0.124Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Apache Tomcat 11.0.28 - 11.0.29
  • Apache Tomcat 10.1.62
  • Apache Tomcat 9.0.124
  • Tomcat clusters using TLS 1.3 with TLS-PSK

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. The vulnerability involves an authentication bypass in Tomcat cluster nodes joining via TLS 1.3 with pre-shared keys, which is a non-HTTP network protocol interaction. Such traffic cannot be reliably distinguished or filtered by a web application firewall.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
CISA SSVC
exploitation none, automatable yes, technical impact totalAssessed by CISA 20 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 19 Nov 2026Published
  2. 20 Nov 2026CISA SSVC assessment: exploitation nonesame day later
  3. 21 Nov 2026First proof-of-concept repository on GitHub (unvetted)1 day later
  4. 21 Nov 2026CVE record last updatedsame day later
  5. 21 Nov 2026Analysed by vulneraibility.comsame day later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2026-133325 being exploited?

Not confirmed. CVE-2026-133325 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.57% probability of exploitation in the next 30 days.

How severe is CVE-2026-133325?

CVE-2026-133325 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-133325?

Yes. A fix has been recorded for CVE-2026-133325. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-133325 affect?

CVE-2026-133325 affects Apache Tomcat 11.0.28 - 11.0.29, Apache Tomcat 10.1.62, Apache Tomcat 9.0.124, Tomcat clusters using TLS 1.3 with TLS-PSK. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-133325?

Upgrade to 11.0.30/10.1.63/9.0.125 or revert cluster to TLS1.2+PSK until fixed

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

1 reference in the CVE record, grouped by the tags the record gives them.

Advisories (1)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.