Skip to main content
Mallory
MediumVulnerability

CVE-2026-34500: Apache Tomcat CLIENT_CERT OCSP Soft-Fail Authentication Bypass

Published Apr 9, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3.1
EPSS0.46%40th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Apache Software Foundation
IdentifiersCVE-2026-34500CWE-295

CVE-2026-34500 is an improper certificate-validation vulnerability in Apache Tomcat CLIENT_CERT authentication. When the Foreign Function and Memory (FFM) API is used, OCSP validation can soft-fail in some scenarios even when an administrator has disabled soft-fail behavior. As a result, CLIENT_CERT authentication may not fail when certificate validation should reject it. Affected releases are Tomcat 11.0.0-M14 through 11.0.20, 10.1.22 through 10.1.53, and 9.0.92 through 9.0.116.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Certificate-validation failures may not cause CLIENT_CERT authentication to be rejected. This can result in unexpected successful authentication and compromise access controls in affected configurations.

Mitigation

If you can’t patch tonight, do this now.

No temporary product workaround is specified. Until patched, limit exposure of affected Tomcat deployments that use CLIENT_CERT authentication with FFM and have soft-fail disabled.

Remediation

Patch, then assume compromise.

Upgrade Apache Tomcat to version 11.0.21 or later on the 11.0.x branch, 10.1.54 or later on the 10.1.x branch, or 9.0.117 or later on the 9.0.x branch.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationTomcatapplication
FAQ

Frequently asked questions

Is CVE-2026-34500 exploited in the wild?
As of Oct 2, 2026, Mallory has no reports of CVE-2026-34500 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-34500?
As of Oct 2, 2026, Mallory has found no public exploit for CVE-2026-34500.
Is there a patch for CVE-2026-34500?
Upgrade Apache Tomcat to version 11.0.21 or later on the 11.0.x branch, 10.1.54 or later on the 10.1.x branch, or 9.0.117 or later on the 9.0.x branch.
What products are affected by CVE-2026-34500?
Apache Software Foundation Tomcat.
How severe is CVE-2026-34500?
CVE-2026-34500 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.46% (40th percentile) as of Oct 2, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity8Community discussion across Reddit, Mastodon, and other social sources.