GHSA-95jq-rwvf-vjx4
CRITICALGHSA-95jq-rwvf-vjx4 is a critical-severity (CVSS 9.1) Improper Authentication vulnerability in org.apache.tomcat:tomcat-coyote-ffm. O3 Security confirms whether GHSA-95jq-rwvf-vjx4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Tomcat: CLIENT_CERT authentication does not fail as expected
Blast Radius
org.apache.tomcat:tomcat-coyote-ffm☕org.apache.tomcat:tomcat-coyote-ffm☕org.apache.tomcat:tomcat-coyote-ffm☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcatReal-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 vulnerability in Apache Tomcat, Apache Tomcat Native.
This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.1.0-M7 through 10.1.52, from 9.0.83 through 9.0.115; Apache Tomcat Native: from 1.1.23 through 1.1.34, from 1.2.0 through 1.2.39, from 1.3.0 through 1.3.6, from 2.0.0 through 2.0.13.
Users are recommended to upgrade to version Tomcat Native 1.3.7 or 2.0.14 and Tomcat 11.0.20, 10.1.53 and 9.0.116, which fix the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat:tomcat-coyote-ffm | ≥ 9.0.83&&< 9.0.116 | 9.0.116 |
| ☕Maven | org.apache.tomcat:tomcat-coyote-ffm | ≥ 10.1.0-M7&&< 10.1.53 | 10.1.53 |
| ☕Maven | org.apache.tomcat:tomcat-coyote-ffm | ≥ 11.0.0-M1&&< 11.0.20 | 11.0.20 |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 9.0.83&&< 9.0.116 | 9.0.116 |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 10.1.0-M7&&< 10.1.53 | 10.1.53 |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 11.0.0-M1&&< 11.0.20 | 11.0.20 |
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.116 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-95jq-rwvf-vjx4 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 GHSA-95jq-rwvf-vjx4 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 GHSA-95jq-rwvf-vjx4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-95jq-rwvf-vjx4 in your dependencies?
O3 detects GHSA-95jq-rwvf-vjx4 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.