dbcve.org
TomcatWeb server / proxy · Apache

CVE-2026-24734

HIGH · 7.5 CVSS v3.1 Published 2026-02-17
Fix available
A fix is available. Upgrade to 1.3.5 / 2.0.12 or later.
See remediation →
84/100
Remediation priority · High
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
Improper Input Validation vulnerability in Apache Tomcat Native, Apache Tomcat. When using an OCSP responder, Tomcat Native (and Tomcat's FFM port of the Tomcat Native code) did not complete verification or freshness checks on the OCSP response which could allow certificate revocation to be bypassed. This issue affects Apache Tomcat Native:  from 1.3.0 through 1.3.4, from 2.0.0 through 2.0.11; Apache Tomcat: from 11.0.0-M1 through 11.0.17, from 10.1.0-M7 through 10.1.51, from 9.0.83 through 9.0.114. The following versions were EOL at the time the CVE was created but are known to be affected: from 1.1.23 through 1.1.34, from 1.2.0 through 1.2.39. Older EOL versions are not affected. Apache Tomcat Native users are recommended to upgrade to versions 1.3.5 or later or 2.0.12 or later, which fix the issue. Apache Tomcat users are recommended to upgrade to versions 11.0.18 or later, 10.1.52 or later or 9.0.115 or later 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

Apache Tomcat Native's OCSP (Online Certificate Status Protocol) responder implementation fails to perform verification and freshness checks on OCSP responses, allowing potentially revoked certificates to be accepted as valid and bypassing certificate revocation checks.

MitigationUpgrade Apache Tomcat Native to version 1.3.5+/2.0.12+ and Apache Tomcat to 11.0.18+/10.1.52+/9.0.115+ to fix the OCSP validation flaw; alternatively, disable OCSP and use CRL-based certificate revocation.

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.115>= 10.1.1, < 10.1.52>= 11.0.1, < 11.0.18= 10.1.0= 11.0.0
Tomcat NativeWeb server / proxy
Affected:>= 1.3.0, < 1.3.5>= 2.0.0, < 2.0.12

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Check Apache Tomcat version
    Run the version.sh (Unix) or version.bat (Windows) script in the Tomcat bin directory, or examine the bootstrap JAR files in the lib folder
    Affected if version is 9.0.83 through 9.0.114, or 10.1.0, or 10.1.1 through 10.1.51, or 11.0.0, or 11.0.1 through 11.0.17 (older than 9.0.115, 10.1.52, or 11.0.18 respectively)
  2. Check Apache Tomcat Native version
    Locate the native library file: tcnative-1.dll on Windows or libtcnative-1.so on Linux, typically in the Tomcat bin or lib directory, or check the tcnative JAR if packaged separately
    Affected if version is 1.3.0 through 1.3.4, or 2.0.0 through 2.0.11 (older than 1.3.5 or 2.0.12)
  3. Determine if OCSP is enabled for certificate validation
    Inspect the server.xml SSL connector configuration for OCSP-related attributes such as ocspEnabled="true" or check for JVM system properties like -Dcom.sun.security.enableOcsp=true, or review the openssl.cnf for OCSP responder configuration
    Affected if OCSP is explicitly enabled for certificate revocation checking in the connector or via system properties

You are affected if you run a vulnerable combination of Apache Tomcat and Apache Tomcat Native versions AND have OCSP-based certificate revocation checking enabled in your SSL/TLS configuration.

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.5 / 2.0.12 / 9.0.115 or later
Fixed in 1.3.52.0.129.0.115
Interim mitigation

Upgrade Apache Tomcat Native to version 1.3.5+/2.0.12+ and Apache Tomcat to 11.0.18+/10.1.52+/9.0.115+ to fix the OCSP validation flaw; alternatively, disable OCSP and use CRL-based certificate revocation.

Recommended fix High confidence

Tomcat 9.0.115 / 10.1.52 / 11.0.18 or Tomcat Native 1.3.5 / 2.0.12

  1. Identify whether you are using Apache Tomcat Native, Apache Tomcat, or both.
  2. If using Apache Tomcat Native: Upgrade to version 1.3.5 or later, or 2.0.12 or later.
  3. If using Apache Tomcat: Upgrade to version 9.0.115 or later (for 9.x), 10.1.52 or later (for 10.1.x), or 11.0.18 or later (for 11.x).
  4. After upgrading, verify that OCSP validation is working correctly in your environment.
  5. Test the certificate revocation functionality to ensure the vulnerability is remediated.

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

Fix this in Tomcat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24734 — 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-24734 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