# CVE-2026-24734: Apache Tomcat Native, Apache Tomcat: OCSP revocation bypass

> Attackers can bypass certificate revocation checks in Apache Tomcat when OCSP is enabled, allowing revoked certificates to be accepted.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Feb 2026
- **Updated:** 15 Jul 2026
- **Also known as:** ALSA-2026:19054, BIT-tomcat-2026-24734, CLEANSTART-2026-ZP28661, CLSA-2026-1774442729, DEBIAN-CVE-2026-24734, GHSA-mgp5-rv84-w37q, MINI-23ph-hf4j-547p, MINI-5hq4-9mr4-mph6, MINI-8448-qxq7-2825, MINI-jj28-mprh-8w2h, MINI-q3q8-vw54-6hjh, MINI-qj85-qccv-g3gc, RHSA-2026:19054, RHSA-2026:5611, RLSA-2026:19054, RLSA-2026:26323, ROOT-APP-MAVEN-CVE-2026-24734, UBUNTU-CVE-2026-24734

## What is CVE-2026-24734?

CVE-2026-24734 is a high-severity vulnerability in Apache Tomcat, published on 17 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-295 (Improper Certificate Validation), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-24734?

13 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core, tomcat and org.apache.tomcat:tomcat-coyote. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 10.1.0-M7 | 10.1.52 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 10.1.0-M7 | 10.1.52 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 11.0.0-M1 | 11.0.18 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 11.0.0-M1 | 11.0.18 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.83 | 9.0.115 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.83 | 9.0.115 |
| `tomcat` | Bitnami | From 9.0.83 | 9.0.115, 10.1.52, 11.0.18 |
| `org.apache.tomcat:tomcat-coyote` | Maven | From 10.1.0-M7 | 10.1.52 |
| `org.apache.tomcat:tomcat-coyote` | Maven | From 10.1.0-M7 | 10.1.52 |
| `org.apache.tomcat:tomcat-coyote` | Maven | From 11.0.0-M1 | 11.0.18 |
| `org.apache.tomcat:tomcat-coyote` | Maven | From 11.0.0-M1 | 11.0.18 |
| `org.apache.tomcat:tomcat-coyote` | Maven | From 9.0.83 | 9.0.115 |
| `org.apache.tomcat:tomcat-coyote` | Maven | From 9.0.83 | 9.0.115 |
| `tomcat` | AlmaLinux:10 | All versions | 1:10.1.49-1.el10_2.1.alma.1 |
| `tomcat-admin-webapps` | AlmaLinux:10 | All versions | 1:10.1.49-1.el10_2.1.alma.1 |
| `tomcat-docs-webapp` | AlmaLinux:10 | All versions | 1:10.1.49-1.el10_2.1.alma.1 |
| `tomcat-el-5.0-api` | AlmaLinux:10 | All versions | 1:10.1.49-1.el10_2.1.alma.1 |
| `tomcat-jsp-3.1-api` | AlmaLinux:10 | All versions | 1:10.1.49-1.el10_2.1.alma.1 |
| `tomcat-lib` | AlmaLinux:10 | All versions | 1:10.1.49-1.el10_2.1.alma.1 |
| `tomcat-servlet-6.0-api` | AlmaLinux:10 | All versions | 1:10.1.49-1.el10_2.1.alma.1 |
| `tomcat-webapps` | AlmaLinux:10 | All versions | 1:10.1.49-1.el10_2.1.alma.1 |
| `tomcat` | Red Hat:enterprise_linux:10.2 | All versions | 1:10.1.49-1.el10_2.1 |
| `tomcat-admin-webapps` | Red Hat:enterprise_linux:10.2 | All versions | 1:10.1.49-1.el10_2.1 |
| `tomcat-docs-webapp` | Red Hat:enterprise_linux:10.2 | All versions | 1:10.1.49-1.el10_2.1 |
| `tomcat-el-5.0-api` | Red Hat:enterprise_linux:10.2 | All versions | 1:10.1.49-1.el10_2.1 |
| `tomcat-jsp-3.1-api` | Red Hat:enterprise_linux:10.2 | All versions | 1:10.1.49-1.el10_2.1 |
| `tomcat-lib` | Red Hat:enterprise_linux:10.2 | All versions | 1:10.1.49-1.el10_2.1 |
| `tomcat-servlet-6.0-api` | Red Hat:enterprise_linux:10.2 | All versions | 1:10.1.49-1.el10_2.1 |
| `tomcat-webapps` | Red Hat:enterprise_linux:10.2 | All versions | 1:10.1.49-1.el10_2.1 |
| `jws6-tomcat` | Red Hat:jboss_enterprise_web_server:6.2::el10 | All versions | 0:10.1.49-9.redhat_00007.1.el10jws |
| `jws6-tomcat-admin-webapps` | Red Hat:jboss_enterprise_web_server:6.2::el10 | All versions | 0:10.1.49-9.redhat_00007.1.el10jws |
| `jws6-tomcat-docs-webapp` | Red Hat:jboss_enterprise_web_server:6.2::el10 | All versions | 0:10.1.49-9.redhat_00007.1.el10jws |
| `jws6-tomcat-el-5.0-api` | Red Hat:jboss_enterprise_web_server:6.2::el10 | All versions | 0:10.1.49-9.redhat_00007.1.el10jws |
| `jws6-tomcat-javadoc` | Red Hat:jboss_enterprise_web_server:6.2::el10 | All versions | 0:10.1.49-9.redhat_00007.1.el10jws |
| `jws6-tomcat-jsp-3.1-api` | Red Hat:jboss_enterprise_web_server:6.2::el10 | All versions | 0:10.1.49-9.redhat_00007.1.el10jws |
| `jws6-tomcat-lib` | Red Hat:jboss_enterprise_web_server:6.2::el10 | All versions | 0:10.1.49-9.redhat_00007.1.el10jws |
| `jws6-tomcat-native` | Red Hat:jboss_enterprise_web_server:6.2::el10 | All versions | 0:1.3.6-1.redhat_1.el10jws |
| `jws6-tomcat-native-debuginfo` | Red Hat:jboss_enterprise_web_server:6.2::el10 | All versions | 0:1.3.6-1.redhat_1.el10jws |
| `jws6-tomcat-selinux` | Red Hat:jboss_enterprise_web_server:6.2::el10 | All versions | 0:10.1.49-9.redhat_00007.1.el10jws |
| `jws6-tomcat-servlet-6.0-api` | Red Hat:jboss_enterprise_web_server:6.2::el10 | All versions | 0:10.1.49-9.redhat_00007.1.el10jws |

Products: Apache Tomcat, Apache Tomcat Native.

## How do I fix CVE-2026-24734?

Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 10.1.52, 11.0.18 or 9.0.115.

## Is CVE-2026-24734 being exploited?

There is no known exploitation of CVE-2026-24734 in the wild and no public exploit code.

## Other vulnerabilities in Apache Tomcat

- [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild)
- [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24734 and fix it if it is affected.

What it is: CVE-2026-24734 is a high-severity vulnerability in Apache Tomcat, published on 17 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24734 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0-M7; fixed in 10.1.52
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0-M7; fixed in 10.1.52
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 11.0.0-M1; fixed in 11.0.18
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 11.0.0-M1; fixed in 11.0.18
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.83; fixed in 9.0.115
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.83; fixed in 9.0.115
- tomcat (Bitnami): affected from 9.0.83; fixed in 9.0.115, 10.1.52, 11.0.18
- org.apache.tomcat:tomcat-coyote (Maven): affected from 10.1.0-M7; fixed in 10.1.52
- org.apache.tomcat:tomcat-coyote (Maven): affected from 10.1.0-M7; fixed in 10.1.52
- org.apache.tomcat:tomcat-coyote (Maven): affected from 11.0.0-M1; fixed in 11.0.18
- org.apache.tomcat:tomcat-coyote (Maven): affected from 11.0.0-M1; fixed in 11.0.18
- org.apache.tomcat:tomcat-coyote (Maven): affected from 9.0.83; fixed in 9.0.115

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24734/ (Markdown: https://insights.sbomify.com/CVE-2026-24734/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24734
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24734
- OSV: https://osv.dev/vulnerability/CVE-2026-24734

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24734/
Summaries are generated and may contain mistakes; the official description above is the record.
