VulnerabilityPublished 20 Oct 2026Updated 28 Oct 2026

CVE-2026-74048: Tomcat6 · Not Failing Securely ('Failing Open') vulnerability in Apache Tomcat

Affects tomcat6Source GCVE Database

Authoritative record:CVE-2026-74048· Medium

Not known to be exploited · fixed in 11.0.27 : update tomcat6 when convenient.

Data as of 28 Oct 2026, 22:28 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in 11.0.27

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10tomcat10`pkg:deb/ubuntu/tomcat10?arch=source&distro=stonking`Other threats	Affected 10.1.40-1ubuntu1 – 10.1.57~us1-0ubuntu1 7 affected builds	Fixed in–
Ubuntu 26.10tomcat11`pkg:deb/ubuntu/tomcat11?arch=source&distro=stonking`Other threats	Affected 11.0.18-1 – 11.0.24-1ubuntu1 5 affected builds	Fixed in–
Ubuntu 26.10tomcat9`pkg:deb/ubuntu/tomcat9?arch=source&distro=stonking`Other threats	Affected =9.0.115-1 =9.0.115-1ubuntu1 =9.0.118-1	Fixed in–
Ubuntu 26.04 LTStomcat10`pkg:deb/ubuntu/tomcat10?arch=source&distro=resolute`Other threats	Affected =10.1.40-1ubuntu1 =10.1.40-1ubuntu1.26.04.1 =10.1.55-1ubuntu2~26.04.1	Fixed in–
Ubuntu 26.04 LTStomcat9`pkg:deb/ubuntu/tomcat9?arch=source&distro=resolute`Other threats	Affected 9.0.95-1ubuntu1 – 9.0.118-1~26.04.1 5 affected builds	Fixed in–
Ubuntu 26.04 LTStomcat11`pkg:deb/ubuntu/tomcat11?arch=source&distro=resolute`Other threats	Affected 11.0.6-1 – 11.0.22-2ubuntu2~26.04.1 6 affected builds	Fixed in–

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

Description

Not Failing Securely ('Failing Open') vulnerability in Apache Tomcat. If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS activation fails, Tomcat logs and error but continues to use JSSE in non-FIPS mode with the provided configuration. This issue affects Apache Tomcat: from 11.0.0-M14 through 11.0.26, from 10.1.22 through 10.1.60, from 9.0.92 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.

References

Community reviews

Loading reviews…