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