CVE Tools
Track your stack

CVE-2026-93446

Apache Tomcat: Possible TLS 1.3 connection failures

No known exploitation. EPSS puts it in the 17th percentile. No fix published yet.

CVSS —Not scoredEPSS percentile17th0.3% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFixNone yetNo fix or workaround published

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

  • Apache Software Foundation Apache TomcatAffected: ≥ 11.0.0-M21, ≤ 11.0.26Upgrade to: after 11.0.26Affected: ≥ 10.1.25, ≤ 10.1.60Upgrade to: after 10.1.60Affected: ≥ 9.0.90, ≤ 9.0.122Upgrade to: after 9.0.122Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

Incomplete cleanup vulnerability in Apache Tomcat could cause TLS 1.3 connections to fail intermittently. This issue affects Apache Tomcat: from 11.0.0-M21 through 11.0.26, from 10.1.25 through 10.1.60, from 9.0.90 through 9.0.122. Users are recommended to upgrade to version 11.0.27, 10.1.61 or 9.0.123, which fix the issue.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS17th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.3% chance of exploitation activity in the next 30 days, which ranks it in the 17th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 0 days, from the signal feeds we watch.

  1. Publishedweakness classified, record updated, record updated

Affected products

Technical detail

Weaknesses

Sources

References in the record

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Apache Tomcat, not every advisory.