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