# CVE-2026-86246: Apache Tomcat Native insecure default OpenSSL options

Source: https://junglewise.ai/threats/cve-2026-86246-initialization-of-a-resource-with-an-insecure-default  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-23. Updated: 2026-10-06  
License: CC BY 4.0 with a link back

CVE-2026-86246 · Severity: critical · CVSS 9.1 · Published 2026-09-23

Apache Tomcat Native, a JNI connector library used by Tomcat web servers to improve HTTPS performance, enabled insecure OpenSSL options by default. This weakens the TLS/SSL security of any Tomcat instance using this library, potentially allowing attackers to intercept encrypted traffic or downgrade the security of HTTPS connections.

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

## Quick answers

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

**How severe is CVE-2026-86246?** Critical severity, with a CVSS score of 9.1, published 23 September 2026.

**Which products and versions are affected?** Apache Tomcat Native 2.0.0 through 2.0.15, 1.3.0 through 1.3.8.

**Is there a fix for CVE-2026-86246?** Yes: fixed in Tomcat Native 2.0.16, 1.3.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-86246 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-86246?** Check whether you run Apache Tomcat Native 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 Native 2.0.16, 1.3.9

## Technical details

The vulnerability stems from insecure default initialization of OpenSSL options in Tomcat Native, including ALLOW_CLIENT_RENEGOTIATION, NO_EXTENDED_MASTER_SECRET, IGNORE_UNEXPECTED_EOF, and ALLOW_NO_DHE_KEX. These settings reduce TLS security by enabling client renegotiation attacks, downgrading cipher strength, and ignoring protocol violations. An attacker with network access can exploit this through man-in-the-middle attacks or protocol downgrade attempts without authentication required.

## Affected products

- Apache Tomcat Native 2.0.0 through 2.0.15, 1.3.0 through 1.3.8

## Timeline

- 2026-09-23: disclosed
- 2026-09-23: advisory

## References

- [https://lists.apache.org/thread/dgyvfwb24nbk45ptvlhdyhdhl5o7k5ol](https://lists.apache.org/thread/dgyvfwb24nbk45ptvlhdyhdhl5o7k5ol)
- [http://www.openwall.com/lists/oss-security/2026/09/23/32](http://www.openwall.com/lists/oss-security/2026/09/23/32)

## Related threats

- [Apache Tomcat Native race condition in client certificate verification](https://junglewise.ai/threats/cve-2026-86247-race-condition-within-a-thread-vulnerability-in-apache-tomcat)
- [Apache Tomcat Native buffer over-read in TLS handshake](https://junglewise.ai/threats/cve-2026-86243-buffer-over-read-vulnerability-in-apache-tomcat-native-during-the)
- [Apache Tomcat improper authentication in CLIENT_CERT validation](https://junglewise.ai/threats/cve-2026-29145-apache-tomcat-improper-authentication-in-client-cert-validation)