CVE-2026-34500
MEDIUMCVE-2026-34500 is a medium-severity (CVSS 6.5) Improper Authentication vulnerability in org.apache.tomcat:tomcat-coyote-ffm. O3 Security confirms whether CVE-2026-34500 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Tomcat: OCSP checks sometimes soft-fail with FFM even when soft-fail is disabled
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
org.apache.tomcat:tomcat-coyote-ffm☕org.apache.tomcat:tomcat-coyote-ffm☕org.apache.tomcat:tomcat-coyote-ffmReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat:tomcat-coyote-ffm | ≥ 9.0.92&&< 9.0.117 | 9.0.117 |
| ☕Maven | org.apache.tomcat:tomcat-coyote-ffm | ≥ 10.1.22&&< 10.1.54 | 10.1.54 |
| ☕Maven | org.apache.tomcat:tomcat-coyote-ffm | ≥ 11.0.0-M14&&< 11.0.21 | 11.0.21 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-coyote-ffm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.tomcat:tomcat-coyote-ffm to 9.0.117 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-34500 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-34500 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-34500. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-34500 in your dependencies?
O3 detects CVE-2026-34500 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.