CVE-2026-34500: Tomcat10 · CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is
Affects tomcat10Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 17 Nov 2026, 20:43 UTC
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTStomcat11pkg:deb/ubuntu/tomcat11?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 25.10tomcat10pkg:deb/ubuntu/tomcat10?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10tomcat11pkg:deb/ubuntu/tomcat11?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10tomcat9pkg:deb/ubuntu/tomcat9?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade Apache Tomcat to versions 11.0.21, 10.1.54, or 9.0.117 where the issue is fixed. No other mitigations are indicated. Patch status is confirmed by the vendor's fixed version releases.
Description
A vulnerability in Apache Tomcat affects CLIENT_CERT authentication when soft fail is disabled and FFM is used. The authentication does not fail as expected in certain scenarios, potentially allowing unauthorized access. This issue impacts Apache Tomcat versions from 11.0.0-M14 through 11.0.20, 10.1.22 through 10.1.53, and 9.0.92 through 9.0.116. Upgrading to versions 11.0.21, 10.1.54, or 9.0.117 resolves the issue.