NVD Data Feeds
In September 2023, the NVD plans to retire all legacy data feeds while guiding any remaining data feed users to updated application-programming interfaces (APIs). APIs have many benefits over data feeds and have been the proven and preferred approach to web-based automation for over a decade. For additional information on the NVD API, please visit the developers pages. Click here for more information on the NVD timeline.
APIs and Data Feed Types
The following table contains links and short descriptions for each API or data feed the NVD offers. Please read how to keep up-to-date with NVD data when using the traditional data feeds.
Users of the data feeds provided on this page must have an understanding of the XML and/or JSON standards and XML or JSON related technologies as defined by www.w3.org.
|CVE and CPE APIs||An alternative to the traditional vulnerability data feed files. The APIs are far more flexible and offer a richer dataset in a single interface compared to the JSON Vulnerability Feeds and CPE Match Feed.|
|JSON Vulnerability Feeds||Each vulnerability in the file includes a description and associated reference links from the CVE® dictionary feed, as well as CVSS base scores, vulnerable product configuration, and weakness categorization.|
|CPE Match Feed||A feed that provides the product/platform applicability statement to CPE URI matching based on the CPEs in the official CPE dictionary.|
|RSS Vulnerability Feeds||An eight day window of security related software flaws.|
|Vulnerability Translation Feeds||Translations of vulnerability feeds.|
|Vulnerability Vendor Comments||Comments provided by vendors regarding a particular flaw affecting within a product.|
|CPE Dictionary||dictionary containing a list of products.|
|Common Configuration Enumeration (CCE) Reference Data||Reference data for common configuration items.|
CVE and CPE APIs
The CVE and CPE APIs are the preferred method for staying up to date with the NVD. Users interested in learning where to begin with the API should visit the NVD developers pages.
Benefits of the APIs over the traditional data feeds include:
- The APIs are updated as frequently as our website (unlike the traditional feeds which have explicit update intervals)
- The APIs provide search capabilities based on the Advanced search feature of the website
- The APIs provide CVE and CPE based searching capabilities, including the ability to search for single CVE and CPE entries
- The ability to view only the information that has changed since a given date or time
- Simplified methods of identifying CPE matches to Applicability statements
|CVE API Documentation||CPE API Documentation|
|Automation Support for CVE Retrieval||Automation Support for CPE Retrieval|
How to Keep Up-to-Date with the NVD Data Using the Traditional Feeds
The vulnerability feeds provide CVE® data organized by the first four digits of a CVE® identifier (except for the 2002 feeds which include vulnerabilities prior to and including "CVE-2002-"). If you are locally mirroring NVD data, either the APIs or the data feeds may be used to stay synchronized. After performing a one-time import of the complete data set using the compressed JSON vulnerability feeds, the "modified" feeds should be used to keep up-to-date.
Each feed is updated nightly, but only if the content of that feed has changed. For example, the 2004 feeds will be updated only if there is an addition or modification to any vulnerability with a starting CVE® identifier of "CVE-2004-". The "recent" feeds are a list of recently published vulnerabilities and the "modified" feeds are a list of recently published and modified vulnerabilities. The "recent" and "modified" feeds only contain vulnerabilities changed within the previous eight days. These feeds are updated approximately every two hours.
Users should always consult the META file to determine if a given feed has been updated since the last import. If no changes have been made there is no benefit to downloading either the .zip or .gz files. This approach should result in a reasonable use of less than 200 requests per day.
Each of the data feeds is described by an associated plain text file with the same name as the .xml file with a .meta extension. These files are updated approximately every two hours to reflect changes within their respective feed file. For example, if the name of the file is nvdcve-1.1-Modified.json then the .meta file name will be nvdcve-1.1-Modified.meta. The .meta file contains information about the specific feed file including the last modified date and time, the size of the file uncompressed, and a SHA256 value of the uncompressed file:
These data feeds includes both previously offered and new NVD data points in an updated JSON format. The "year" feeds are updated once per day, while the "recent" and "modified" feeds are updated every two hours.
In September 2023, the NVD will retire its legacy data feeds while working to guide any remaining data feed users to updated application-programming interfaces (APIs). APIs have many benefits over data feeds and have been the proven and preferred approach to web-based automation for over a decade. For additional information on the NVD API, please visit the developers pages. Click here for more information on the NVD timeline.
NVD JSON 1.1 Schema
|CVE-Modified||03/27/2023; 8:00:00 AM -0400||META|
|CVE-Recent||03/27/2023; 8:00:00 AM -0400||META|
|CVE-2023||03/27/2023; 3:00:01 AM -0400||META|
|CVE-2022||03/27/2023; 3:00:14 AM -0400||META|
|CVE-2021||03/27/2023; 3:00:34 AM -0400||META|
|CVE-2020||03/25/2023; 3:00:52 AM -0400||META|
|CVE-2019||03/25/2023; 3:01:07 AM -0400||META|
|CVE-2018||03/27/2023; 3:00:50 AM -0400||META|
|CVE-2017||03/25/2023; 3:01:31 AM -0400||META|
|CVE-2016||03/26/2023; 3:00:33 AM -0400||META|
|CVE-2015||03/26/2023; 3:00:41 AM -0400||META|
|CVE-2014||03/16/2023; 3:02:19 AM -0400||META|
|CVE-2013||03/16/2023; 3:02:28 AM -0400||META|
|CVE-2012||03/24/2023; 3:01:24 AM -0400||META|
|CVE-2011||02/17/2023; 3:02:23 AM -0500||META|
|CVE-2010||03/04/2023; 3:02:49 AM -0500||META|
|CVE-2009||03/04/2023; 3:02:56 AM -0500||META|
|CVE-2008||03/14/2023; 3:04:06 AM -0400||META|
|CVE-2007||03/08/2023; 3:02:33 AM -0500||META|
|CVE-2006||03/14/2023; 3:04:20 AM -0400||META|
|CVE-2005||03/04/2023; 3:03:10 AM -0500||META|
|CVE-2004||03/25/2023; 3:01:50 AM -0400||META|
|CVE-2003||12/14/2022; 3:02:58 AM -0500||META|
|CVE-2002||03/08/2023; 3:02:39 AM -0500||META|
CPE Match Feed
This data feed provides a list of all CVE applicability statement match criteria (CPE match strings and CPE match ranges) and the CPE URIs from the official CPE dictionary that match. Data consumers can use this feed to enhance the CPE information provided in the JSON Vulnerability feeds. If a CPE URI expected to match a given criteria is missing, please contact email@example.com as those CPEs may need approved to the official CPE dictionary. This feed is updated once per day.
NVD CPE Match Feed 1.0 Schema
|CPE-Match||03/27/2023; 12:10:07 AM -0400||META|
RSS Vulnerability Feeds
In March 2023, The NVD plans to retire the RSS data feeds and pages intended to support web scraping (e.g., Full Listings) before its APIs existed. Users with automated workflows that target such pages must transition to the the 2.0 APIs.
NVD provides two RSS 1.0 data feeds. The first feed, nvd-rss.xml ( zip or gz ), provides information on all vulnerabilities within the previous eight days. The second feed, nvd-rss-analyzed.xml ( zip or gz ), provides only vulnerabilities which have been analyzed within the previous eight days. The advantage of the second feed is that we are able to provide vulnerable product names in the title. The advantage of the former is that you learn about new vulnerabilities as soon as possible.
Vulnerability Vendor Comments
NVD provides a service whereby software development organizations can submit "Official Vendor Comments" on the set of CVE vulnerabilities that apply to their products. Organizations can submit comments by contacting NVD staff at firstname.lastname@example.org . More information is provided on the vendor comment page.
All of the vendors comments can be downloaded from the following XML feed which is updated every 2 hours:
NVD/CVE Translated XML Feed (version 1.0)
NVD provides an XML feed for translations of CVE vulnerabilities into other languages.
Currently, INCIBE (Spanish National Cybersecurity Institute) is translating vulnerabilities into Spanish. INCIBE is solely responsible for the Spanish translation content.
NVD/CVE Translation XML Schema
|CVE-Modified||03/27/2023; 12:40:00 AM -0400||META|
|GZ||< 0.01 MB|
|ZIP||< 0.01 MB|
|CVE-2023||03/27/2023; 12:35:00 AM -0400||META|
|GZ||< 0.01 MB|
|ZIP||< 0.01 MB|
|CVE-2022||03/27/2023; 12:35:27 AM -0400||META|
|CVE-2021||03/27/2023; 12:36:04 AM -0400||META|
|CVE-2020||03/27/2023; 12:36:37 AM -0400||META|
|CVE-2019||03/27/2023; 12:37:04 AM -0400||META|
|CVE-2018||03/27/2023; 12:37:32 AM -0400||META|
|CVE-2017||03/27/2023; 12:37:58 AM -0400||META|
|CVE-2016||03/27/2023; 12:38:15 AM -0400||META|
|CVE-2015||03/27/2023; 12:38:29 AM -0400||META|
|CVE-2014||03/27/2023; 12:38:44 AM -0400||META|
|CVE-2013||03/27/2023; 12:38:55 AM -0400||META|
|CVE-2012||03/27/2023; 12:39:05 AM -0400||META|
|CVE-2011||03/27/2023; 12:39:13 AM -0400||META|
|CVE-2010||03/27/2023; 12:39:23 AM -0400||META|
|CVE-2009||03/27/2023; 12:39:32 AM -0400||META|
|CVE-2008||03/27/2023; 12:39:44 AM -0400||META|
|CVE-2007||03/27/2023; 12:39:56 AM -0400||META|
|CVE-2006||03/27/2023; 12:40:04 AM -0400||META|
|CVE-2005||03/27/2023; 12:40:05 AM -0400||META|
|CVE-2004||03/27/2023; 12:40:07 AM -0400||META|
|CVE-2003||03/27/2023; 12:40:09 AM -0400||META|
|CVE-2002||03/27/2023; 12:40:11 AM -0400||META|