CVE-2026-24734: CWE-20 Improper Input Validation in Apache Software Foundation Apache Tomcat Native
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.
AI Analysis
Technical Summary
CVE-2026-24734 identifies a critical improper input validation vulnerability (CWE-20) in the Apache Tomcat Native library and Apache Tomcat server software, specifically in the handling of Online Certificate Status Protocol (OCSP) responses. OCSP is used to verify the revocation status of X.509 digital certificates in TLS communications. The vulnerability occurs because Tomcat Native and the FFM port of Tomcat Native code do not fully verify the OCSP response or check its freshness, meaning the server may accept stale or tampered OCSP responses. This flaw effectively allows attackers to bypass certificate revocation checks, enabling the acceptance of revoked certificates. Such a bypass can facilitate man-in-the-middle (MITM) attacks, where an attacker uses a revoked certificate to impersonate a legitimate server or intercept encrypted communications. The affected versions span Apache Tomcat Native from 1.3.0 through 1.3.4 and 2.0.0 through 2.0.11, and Apache Tomcat from 9.0.83 through 9.0.114, 10.1.0-M7 through 10.1.51, and 11.0.0-M1 through 11.0.17. Older EOL versions from 1.1.23 through 1.2.39 are also affected. No CVSS score has been assigned yet, and no exploits have been observed in the wild. The Apache Software Foundation recommends upgrading to versions 1.3.5 or later, 2.0.12 or later for Tomcat Native, and 9.0.115, 10.1.52, or 11.0.18 or later for Apache Tomcat to remediate the issue. This vulnerability undermines the integrity and confidentiality of TLS sessions relying on OCSP, posing a significant security risk for environments using affected versions without patching.
Potential Impact
For European organizations, this vulnerability poses a significant risk to secure communications that rely on Apache Tomcat and Tomcat Native for web services and applications. Since OCSP is a widely used protocol for certificate revocation checking, bypassing these checks can allow attackers to present revoked certificates as valid, facilitating man-in-the-middle attacks, data interception, and impersonation of trusted services. This can lead to unauthorized data access, leakage of sensitive information, and compromise of user trust. Sectors such as finance, healthcare, government, and critical infrastructure that rely heavily on secure TLS communications are particularly at risk. The impact is exacerbated in environments where certificate revocation is a critical part of the security posture. Additionally, since Apache Tomcat is a popular Java servlet container used extensively across Europe, the scope of affected systems is broad. The absence of known exploits in the wild suggests a window for proactive mitigation, but the potential impact on confidentiality and integrity is high if exploited.
Mitigation Recommendations
European organizations should immediately inventory their use of Apache Tomcat and Tomcat Native to identify affected versions. They must prioritize upgrading to the fixed versions: Apache Tomcat Native 1.3.5 or later, 2.0.12 or later, and Apache Tomcat 9.0.115, 10.1.52, or 11.0.18 or later. Where immediate upgrades are not feasible, organizations should consider disabling OCSP validation temporarily or implementing alternative certificate revocation checking mechanisms such as CRL (Certificate Revocation Lists), though this may reduce security effectiveness. Network-level controls such as strict TLS inspection and monitoring for anomalous certificate usage can help detect exploitation attempts. Additionally, organizations should review their TLS configurations to ensure OCSP stapling is correctly implemented and monitored. Regular security audits and penetration testing focusing on TLS and certificate validation processes are recommended. Finally, organizations should maintain awareness of any emerging exploit reports and apply patches promptly.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Sweden, Poland, Belgium, Austria
CVE-2026-24734: CWE-20 Improper Input Validation in Apache Software Foundation Apache Tomcat Native
Description
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.
AI-Powered Analysis
Technical Analysis
CVE-2026-24734 identifies a critical improper input validation vulnerability (CWE-20) in the Apache Tomcat Native library and Apache Tomcat server software, specifically in the handling of Online Certificate Status Protocol (OCSP) responses. OCSP is used to verify the revocation status of X.509 digital certificates in TLS communications. The vulnerability occurs because Tomcat Native and the FFM port of Tomcat Native code do not fully verify the OCSP response or check its freshness, meaning the server may accept stale or tampered OCSP responses. This flaw effectively allows attackers to bypass certificate revocation checks, enabling the acceptance of revoked certificates. Such a bypass can facilitate man-in-the-middle (MITM) attacks, where an attacker uses a revoked certificate to impersonate a legitimate server or intercept encrypted communications. The affected versions span Apache Tomcat Native from 1.3.0 through 1.3.4 and 2.0.0 through 2.0.11, and Apache Tomcat from 9.0.83 through 9.0.114, 10.1.0-M7 through 10.1.51, and 11.0.0-M1 through 11.0.17. Older EOL versions from 1.1.23 through 1.2.39 are also affected. No CVSS score has been assigned yet, and no exploits have been observed in the wild. The Apache Software Foundation recommends upgrading to versions 1.3.5 or later, 2.0.12 or later for Tomcat Native, and 9.0.115, 10.1.52, or 11.0.18 or later for Apache Tomcat to remediate the issue. This vulnerability undermines the integrity and confidentiality of TLS sessions relying on OCSP, posing a significant security risk for environments using affected versions without patching.
Potential Impact
For European organizations, this vulnerability poses a significant risk to secure communications that rely on Apache Tomcat and Tomcat Native for web services and applications. Since OCSP is a widely used protocol for certificate revocation checking, bypassing these checks can allow attackers to present revoked certificates as valid, facilitating man-in-the-middle attacks, data interception, and impersonation of trusted services. This can lead to unauthorized data access, leakage of sensitive information, and compromise of user trust. Sectors such as finance, healthcare, government, and critical infrastructure that rely heavily on secure TLS communications are particularly at risk. The impact is exacerbated in environments where certificate revocation is a critical part of the security posture. Additionally, since Apache Tomcat is a popular Java servlet container used extensively across Europe, the scope of affected systems is broad. The absence of known exploits in the wild suggests a window for proactive mitigation, but the potential impact on confidentiality and integrity is high if exploited.
Mitigation Recommendations
European organizations should immediately inventory their use of Apache Tomcat and Tomcat Native to identify affected versions. They must prioritize upgrading to the fixed versions: Apache Tomcat Native 1.3.5 or later, 2.0.12 or later, and Apache Tomcat 9.0.115, 10.1.52, or 11.0.18 or later. Where immediate upgrades are not feasible, organizations should consider disabling OCSP validation temporarily or implementing alternative certificate revocation checking mechanisms such as CRL (Certificate Revocation Lists), though this may reduce security effectiveness. Network-level controls such as strict TLS inspection and monitoring for anomalous certificate usage can help detect exploitation attempts. Additionally, organizations should review their TLS configurations to ensure OCSP stapling is correctly implemented and monitored. Regular security audits and penetration testing focusing on TLS and certificate validation processes are recommended. Finally, organizations should maintain awareness of any emerging exploit reports and apply patches promptly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-01-26T14:20:56.965Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 699575bd80d747be205377f0
Added to database: 2/18/2026, 8:18:05 AM
Last enriched: 2/18/2026, 8:24:15 AM
Last updated: 2/20/2026, 11:53:18 PM
Views: 349
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.
Related Threats
CVE-2026-27203: CWE-15: External Control of System or Configuration Setting in YosefHayim ebay-mcp
HighCVE-2026-27168: CWE-122: Heap-based Buffer Overflow in HappySeaFox sail
HighCVE-2026-27134: CWE-287: Improper Authentication in strimzi strimzi-kafka-operator
HighCVE-2026-27190: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in denoland deno
HighCVE-2026-27026: CWE-770: Allocation of Resources Without Limits or Throttling in py-pdf pypdf
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.