Not Failing Securely ('Failing Open') Affecting tomcat11 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.24% (14th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-TOMCAT11-21281884
  • published21 Oct 2026
  • disclosed20 Oct 2026

Introduced: 20 Oct 2026

NewCVE-2026-74048  (opens in a new tab)
CWE-636  (opens in a new tab)

How to fix?

There is no fixed version for Debian:unstable tomcat11.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tomcat11 package and not the tomcat11 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1