dbcve.org
TomcatWeb server / proxy · Apache

CVE-2026-29145

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 1.3.7 / 2.0.14 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CLIENT_CERT authentication does not fail as expected for certain scenarios when soft fail is disabled in Apache Tomcat and Apache Tomcat Native. This could allow authentication bypass or improper handling of certificate-based authentication, leading to unauthorized access.

MitigationUpgrade to Tomcat 9.0.116 / 10.1.53 / 11.0.20 and Tomcat Native 1.3.7 / 2.0.14 or later to resolve the authentication failure logic issue.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TomcatWeb server / proxy
Affected:>= 9.0.83, < 9.0.116>= 10.1.1, < 10.1.53>= 11.0.0, < 11.0.20= 10.1.0
Tomcat NativeWeb server / proxy
Affected:>= 1.1.23, < 1.3.7>= 2.0.0, < 2.0.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Tomcat version
    Run the version.sh script in Tomcat's bin directory or check serverinfo.properties in the lib folder. Look for version numbers in the format 9.0.x, 10.1.x, or 11.0.x.
    Affected if The installed version is 9.0.83 through 9.0.115, 10.1.0, 10.1.1 through 10.1.52, or 11.0.0 through 11.0.19.
  2. Identify Apache Tomcat Native version
    Check for the tomcat-native library (typically libtcnative-1.so, libtcnative-1.dylib, or tcnative-1.dll) and run 'ldd' or check file properties to identify the version. Alternatively, check logs for loaded native library version at startup.
    Affected if Tomcat Native version is 1.1.23 through 1.3.6, or 2.0.0 through 2.0.13.
  3. Verify CLIENT_CERT authentication is configured
    Inspect the server.xml configuration file in the Tomcat conf directory. Look for <Connector> elements with clientAuth attribute set to 'true' or 'want', or check <Realm> elements with className="org.apache.catalina.realm.JNDIRealm" or similar with clientCertMode="CLIENT-CERT".
    Affected if CLIENT_CERT authentication is configured in the Tomcat connector or realm settings.
  4. Check if soft fail is disabled for SSL
    In server.xml, examine the <Connector> element configured for CLIENT_CERT. Check for SSLEnabled="true" with attributes like truststoreFile/truststorePass configured. Look for absence of 'softFail="true"' in the SSL configuration, which indicates soft fail is disabled (default behavior).
    Affected if SSL is enabled for CLIENT_CERT authentication without the softFail parameter set to true.

You are affected if your environment runs Apache Tomcat in an affected version range (9.0.83-9.0.115, 10.1.0, 10.1.1-10.1.52, or 11.0.0-11.0.19) or Tomcat Native in an affected version range (1.1.23-1.3.6 or 2.0.0-2.0.13), AND uses CLIENT_CERT authentication with SSL and soft fail disabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.3.7 / 2.0.14 / 9.0.116 or later
Fixed in 1.3.72.0.149.0.116
Interim mitigation

Upgrade to Tomcat 9.0.116 / 10.1.53 / 11.0.20 and Tomcat Native 1.3.7 / 2.0.14 or later to resolve the authentication failure logic issue.

Recommended fix High confidence

Tomcat 9.0.116, 10.1.53, or 11.0.20 (whichever branch is in use) + Tomcat Native 1.3.7 or 2.0.14

  1. 1. Identify current Tomcat version by checking the $CATALINA_HOME/RELEASE-NOTES file or running 'catalina.sh version'
  2. 2. Identify current Tomcat Native version by checking the 'native' library version in the Tomcat Native library directory or server logs
  3. 3. For Tomcat 9.x: Download and install Apache Tomcat 9.0.116 from https://tomcat.apache.org/download-90.cgi
  4. 4. For Tomcat 10.1.x: Download and install Apache Tomcat 10.1.53 from https://tomcat.apache.org/download-10.cgi
  5. 5. For Tomcat 11.x: Download and install Apache Tomcat 11.0.20 from https://tomcat.apache.org/download-11.cgi
  6. 6. Download and install Tomcat Native 1.3.7 or 2.0.14 from https://tomcat.apache.org/download-native.cgi (matching the architecture and OpenSSL version)
  7. 7. Replace the existing tomcat-native library (typically in $CATALINA_HOME/bin/tomcat-native.tar.gz or installed via system package)
  8. 8. Restart Tomcat services to load the new versions
Caveat Major version upgrades of Tomcat (e.g., 9.x to 10.x or 10.x to 11.x) may require application code changes due to javax to jakarta namespace migration; minor version upgrades within the same major branch typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tomcat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29145 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29145 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data