Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-74048 Overview
CVE-2026-74048 is a "failing open" vulnerability in Apache Tomcat affecting the OpenSSLLifecycleListener component. When administrators configure Tomcat to operate in Federal Information Processing Standards (FIPS) mode, a FIPS activation failure does not halt startup. Instead, Tomcat logs an error and silently falls back to the Java Secure Socket Extension (JSSE) in non-FIPS mode using the supplied configuration. The issue is tracked under CWE-636: Not Failing Securely. Deployments subject to FIPS 140-2 or 140-3 compliance mandates may therefore run cryptographic operations under non-approved providers without any functional indication to applications or clients.
Critical Impact
Tomcat continues serving TLS traffic in non-FIPS mode after a failed FIPS initialization, breaking compliance guarantees and masking a cryptographic misconfiguration.
Affected Products
- Apache Tomcat 11.0.0-M14 through 11.0.26
- Apache Tomcat 10.1.22 through 10.1.60
- Apache Tomcat 9.0.92 through 9.0.122
Discovery Timeline
- 2026-10-20 - CVE-2026-74048 published to the National Vulnerability Database
- 2026-10-20 - Advisory posted to the Apache Mailing List Thread and OpenWall OSS-Security Update
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-74048
Vulnerability Analysis
Apache Tomcat exposes OpenSSLLifecycleListener to initialize the OpenSSL-backed TLS stack and enable FIPS mode when administrators request it. The listener attempts to activate the FIPS-approved OpenSSL provider at server startup. If the activation call fails for any reason, such as a missing FIPS module, an unapproved OpenSSL build, or an invalid provider configuration, Tomcat records an error entry and proceeds with initialization. The connector then falls back to JSSE using the supplied keystore, cipher, and protocol configuration. The result is a server that appears healthy and serves TLS traffic, yet operates outside the cryptographic boundary the administrator explicitly requested.
Operators relying on log review to confirm FIPS enforcement may miss the error entry during routine restarts or automated deployments. Downstream clients receive no signal that the negotiated TLS session uses non-approved cryptography.
Root Cause
The defect is a design flaw in the lifecycle listener's error handling path. Rather than aborting startup when FIPS activation fails, the listener treats the failure as recoverable and continues initialization. This behavior maps directly to CWE-636, where a security feature degrades to an insecure default on failure instead of refusing to start.
Attack Vector
The issue is primarily a compliance and assurance failure rather than a direct remote exploitation vector. An attacker is not required to trigger the condition. Any configuration drift, dependency change, or FIPS module failure that prevents activation leaves the server running in non-FIPS mode. Adversaries aware of the fallback could target environments where weaker ciphers or non-approved algorithms become reachable once FIPS enforcement is dropped. Refer to the Apache Mailing List Thread for the upstream description. No public proof-of-concept code is required to reproduce the condition.
Detection Methods for CVE-2026-74048
Indicators of Compromise
- Tomcat catalina.out entries recording a FIPS activation failure from OpenSSLLifecycleListener followed by successful connector startup.
- TLS sessions negotiating cipher suites or protocol versions that are disallowed under FIPS 140-2 or 140-3.
- Absence of OpenSSL FIPS provider initialization messages in startup logs on hosts configured for FIPS mode.
Detection Strategies
- Parse Tomcat startup logs for the specific OpenSSLLifecycleListener FIPS error strings and alert when they appear alongside a running HTTPS connector.
- Perform active TLS scans against Tomcat endpoints and flag any negotiated suite outside the FIPS-approved list.
- Compare the running Tomcat version against the fixed releases 11.0.27, 10.1.61, and 9.0.123 across the fleet.
Monitoring Recommendations
- Centralize Tomcat and JVM logs and build a dashboard that tracks FIPS initialization status per host and restart event.
- Add a startup self-test that queries the active security provider and fails health checks when the expected FIPS provider is absent.
- Review change management events that modify OpenSSL, Java, or Tomcat packages, since these can silently disable FIPS activation.
How to Mitigate CVE-2026-74048
Immediate Actions Required
- Upgrade Apache Tomcat to 11.0.27, 10.1.61, or 9.0.123 depending on the deployed branch.
- Audit all hosts that configure OpenSSLLifecycleListener with FIPS mode and confirm the FIPS provider is active after each restart.
- Treat any historical FIPS activation error in logs as an incident and verify the TLS sessions served during that window.
Patch Information
The Apache Tomcat project resolved the issue in versions 11.0.27, 10.1.61, and 9.0.123. The fix changes the lifecycle listener to fail startup when FIPS activation does not succeed, aligning behavior with the administrator's declared security posture. Patch details are published in the Apache Mailing List Thread and the OpenWall OSS-Security Update.
Workarounds
- Add a startup wrapper that inspects Tomcat logs for FIPS activation errors and terminates the service if any are present.
- Restrict connector configuration to FIPS-approved protocols and cipher suites so that a silent fallback still rejects non-approved negotiations.
- Monitor the active JSSE provider via a scheduled JMX query and alert when it does not match the expected FIPS provider.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

