CVE-2026-29145: Apache Tomcat: CLIENT_CERT authentication does not fail as expected

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 0.7%, percentile 53: FIRST’s model estimates a 0.7% chance of exploitation activity in the next 30 days, higher than 53% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes org.apache.tomcat:tomcat (Maven) >= 9.0.83, < 9.0.116, fixed in 9.0.116; org.apache.tomcat:tomcat (Maven) >= 10.1.0-M7, < 10.1.53, fixed in 10.1.53; org.apache.tomcat:tomcat (Maven) >= 11.0.0-M1, < 11.0.20, fixed in 11.0.20; org.apache.tomcat:tomcat-coyote-ffm (Maven) >= 9.0.83, < 9.0.116, fixed in 9.0.116. Check your lockfile, including transitive dependencies.

What it is

CLIENTCERT 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.

From the GitHub advisory

CLIENTCERT 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.

Weakness type: CWE-287.

Product: org.apache.tomcat:tomcat (Maven) · Assigned by: apache · Published: 2026-04-09

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact partial.
• FIRST EPSS (model of 2026-10-21): 0.71% probability of exploitation activity in the next 30 days; percentile 53.

Timeline

• 2026-04-09 — CVE record published by apache
• 2026-04-09 — GitHub-reviewed advisory GHSA-95jq-rwvf-vjx4 published (critical)
• 2026-04-10 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. lists.apache.org lists.apache.org

Vulnerability records

1. GitHub Advisory GHSA-95jq-rwvf-vjx4 github.com
2. CVE.org record CVE-2026-29145 cve.org
3. NVD entry CVE-2026-29145 nvd.nist.gov

Other references from the CVE record and advisory

1. openwall.com openwall.com
2. github.com github.com
3. github.com github.com
4. github.com github.com
5. tomcat.apache.org tomcat.apache.org
6. tomcat.apache.org tomcat.apache.org
7. tomcat.apache.org tomcat.apache.org

Critical Maven advisories · Today’s Security Digest