Quick answers
- Is CVE-2026-86248 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86248 being exploited in the wild.
- How severe is CVE-2026-86248?
- Critical severity, with a CVSS score of 9.8, published 23 September 2026.
- Which products and versions are affected?
- Apache Tomcat 11.0.0-M14 through 11.0.25, 10.1.22 through 10.1.59, 9.0.92 through 9.0.121.
- Is there a fix for CVE-2026-86248?
- A patch was published on 2026-09-23: Patches released: 11.0.26, 10.1.60, 9.0.122 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86248 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86248?
- 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.
Technical details
The vulnerability exists in Tomcat's CLIENT_CERT authentication mechanism where certain authentication failure scenarios are not properly handled when soft-fail is disabled, resulting in requests proceeding without proper validation. The issue affects the authentication filter's enforcement logic and can be triggered via network requests to applications configured with mandatory client certificate authentication. A patch is available in Tomcat 11.0.26, 10.1.60, and 9.0.122.
Affected products
- Apache Tomcat 11.0.0-M14 through 11.0.25, 10.1.22 through 10.1.59, 9.0.92 through 9.0.121
Timeline
- 2026-09-23: disclosed
- 2026-09-23: patched: Patches released: 11.0.26, 10.1.60, 9.0.122