Summary
CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled and FFM is used in Apache Tomcat.
This issue affects Apache Tomcat: from 11.0.0-M14 through 11.0.20, from 10.1.22 through 10.1.53, from 9.0.92 through 9.0.116.
Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fixes the issue.
Impact
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
CVE-2026-34500 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.0.117, 10.1.54, 11.0.21); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
org.apache.tomcat:tomcat-coyote-ffm to 9.0.117 or later; org.apache.tomcat:tomcat-coyote-ffm to 10.1.54 or later; org.apache.tomcat:tomcat-coyote-ffm to 11.0.21 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-34500? CVE-2026-34500 is a medium-severity improper authentication vulnerability in org.apache.tomcat:tomcat-coyote-ffm (maven), affecting versions >= 9.0.92, < 9.0.117. It is fixed in 9.0.117, 10.1.54, 11.0.21. The application does not adequately verify the identity of a user, device, or process before granting access.
- How severe is CVE-2026-34500? CVE-2026-34500 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.apache.tomcat:tomcat-coyote-ffm are affected by CVE-2026-34500? org.apache.tomcat:tomcat-coyote-ffm (maven) versions >= 9.0.92, < 9.0.117 is affected.
- Is there a fix for CVE-2026-34500? Yes. CVE-2026-34500 is fixed in 9.0.117, 10.1.54, 11.0.21. Upgrade to this version or later.
- Is CVE-2026-34500 exploitable, and should I be worried? Whether CVE-2026-34500 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-34500 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-34500?
- Upgrade
org.apache.tomcat:tomcat-coyote-ffmto 9.0.117 or later - Upgrade
org.apache.tomcat:tomcat-coyote-ffmto 10.1.54 or later - Upgrade
org.apache.tomcat:tomcat-coyote-ffmto 11.0.21 or later
- Upgrade