CVE-2026-29145: CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled in Apache Software Foundation Apache Tomcat
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.
AI Analysis
Technical Summary
The vulnerability CVE-2026-29145 affects Apache Tomcat and Apache Tomcat Native components where CLIENT_CERT authentication does not fail as intended under specific conditions when the soft fail option is disabled. This improper failure behavior can lead to authentication bypass or incorrect authentication outcomes. Affected versions include Apache Tomcat from 11.0.0-M1 through 11.0.18, 10.1.0-M7 through 10.1.52, and 9.0.83 through 9.0.115, as well as Apache Tomcat Native versions from 1.1.23 through 1.1.34, 1.2.0 through 1.2.39, 1.3.0 through 1.3.6, and 2.0.0 through 2.0.13. The Apache Software Foundation recommends upgrading to Tomcat Native 1.3.7 or 2.0.14 and Tomcat 11.0.20, 10.1.53, and 9.0.116 to remediate this issue.
Potential Impact
The impact of this vulnerability is that CLIENT_CERT authentication may not fail as expected, potentially allowing unauthorized users to bypass authentication checks or causing authentication to succeed incorrectly. This could lead to unauthorized access to applications running on affected Apache Tomcat servers. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrading to the fixed versions is the recommended remediation. Users should upgrade Apache Tomcat to versions 11.0.20, 10.1.53, or 9.0.116 and Apache Tomcat Native to versions 1.3.7 or 2.0.14. No other mitigation or temporary workaround is indicated in the advisory. Patch status is confirmed by the vendor advisory recommending these upgrades.
CVE-2026-29145: CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled in Apache Software Foundation Apache Tomcat
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-29145 affects Apache Tomcat and Apache Tomcat Native components where CLIENT_CERT authentication does not fail as intended under specific conditions when the soft fail option is disabled. This improper failure behavior can lead to authentication bypass or incorrect authentication outcomes. Affected versions include Apache Tomcat from 11.0.0-M1 through 11.0.18, 10.1.0-M7 through 10.1.52, and 9.0.83 through 9.0.115, as well as Apache Tomcat Native versions from 1.1.23 through 1.1.34, 1.2.0 through 1.2.39, 1.3.0 through 1.3.6, and 2.0.0 through 2.0.13. The Apache Software Foundation recommends upgrading to Tomcat Native 1.3.7 or 2.0.14 and Tomcat 11.0.20, 10.1.53, and 9.0.116 to remediate this issue.
Potential Impact
The impact of this vulnerability is that CLIENT_CERT authentication may not fail as expected, potentially allowing unauthorized users to bypass authentication checks or causing authentication to succeed incorrectly. This could lead to unauthorized access to applications running on affected Apache Tomcat servers. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrading to the fixed versions is the recommended remediation. Users should upgrade Apache Tomcat to versions 11.0.20, 10.1.53, or 9.0.116 and Apache Tomcat Native to versions 1.3.7 or 2.0.14. No other mitigation or temporary workaround is indicated in the advisory. Patch status is confirmed by the vendor advisory recommending these upgrades.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-03-04T09:52:45.179Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d7ff941cc7ad14da10e9cb
Added to database: 4/9/2026, 7:35:48 PM
Last enriched: 4/9/2026, 7:51:44 PM
Last updated: 4/10/2026, 8:15:32 AM
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.