# CVE-2026-74048: Apache Tomcat FIPS mode validation not failing securely

Source: https://junglewise.ai/threats/cve-2026-74048-not-failing-securely-failing-open-vulnerability-in-apache-tomcat  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-20. Updated: 2026-10-20  
License: CC BY 4.0 with a link back

CVE-2026-74048 · Severity: info · Published 2026-10-20

Apache Tomcat is a web application server used to run Java-based web services. When configured to enforce FIPS cryptographic mode for security compliance, Tomcat may fail to activate FIPS correctly but continues running anyway, silently using standard cryptography instead. This can result in organizations unknowingly operating outside their required security or compliance standards.

Technologies: [Apache Tomcat](https://junglewise.ai/threats/technologies/tomcat). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-74048 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-74048 being exploited in the wild.

**How severe is CVE-2026-74048?** Informational severity, published 20 October 2026.

**Which products and versions are affected?** Apache Tomcat 11.0.0-M14 through 11.0.26, 10.1.22 through 10.1.60, 9.0.92 through 9.0.122.

**Is there a fix for CVE-2026-74048?** Yes: fixed in Tomcat 11.0.27, 10.1.61, 9.0.123. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-74048 attacked?** It is attacked with local access, in a web application.

**Am I affected by CVE-2026-74048?** Check whether you run Apache Tomcat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Tomcat 11.0.27, 10.1.61, 9.0.123

## Technical details

The OpenSSLLifecycleListener in Apache Tomcat, when configured for FIPS mode, fails to enforce cryptographic compliance if FIPS activation fails. Instead of halting startup, Tomcat logs an error and falls back to JSSE in non-FIPS mode, allowing the server to operate with weaker cryptographic validation. No authentication or network access is required to trigger this condition; it occurs during server initialization when FIPS mode is requested but unavailable.

## Affected products

- Apache Tomcat 11.0.0-M14 through 11.0.26, 10.1.22 through 10.1.60, 9.0.92 through 9.0.122

## Timeline

- 2026-10-20: disclosed

## References

- [https://lists.apache.org/thread.html/v5ry0sx1c7x1wr5mx4cddj3p3mv1ho6m](https://lists.apache.org/thread.html/v5ry0sx1c7x1wr5mx4cddj3p3mv1ho6m)

## Related threats

- [Apache Tomcat Jakarta Security credential handler bypass](https://junglewise.ai/threats/cve-2026-111248-the-jakarta-security-identity-store-backed-by-the-tomcat-user)
- [Apache Tomcat incomplete cleanup in TLS 1.3 connections](https://junglewise.ai/threats/cve-2026-93446-incomplete-cleanup-vulnerability-in-apache-tomcat-could-cause-tls)
- [Apache Tomcat HTTP trailer information leak between requests](https://junglewise.ai/threats/cve-2026-88041-incomplete-cleanup-vulnerability-in-apache-tomcat-allowed-an)
- [Apache Tomcat TOCTOU race condition in APR/Native connector](https://junglewise.ai/threats/cve-2026-80353-time-of-check-time-of-use-toctou-race-condition-vulnerability-in)
- [Apache Tomcat Execution After Redirect vulnerability](https://junglewise.ai/threats/cve-2026-74049-execution-after-redirect-ear-vulnerability-in-apache-tomcat-this)