NVD Data Feeds

APIs and Data Feed Types

The following table contains quick links and descriptions to each API or data feed type we offer. Please make sure to read about how to keep up-to-date with NVD data when using the traditional data feeds at the bottom of this page!

CVE and CPE APIs

The CVE and CPE APIs are the next stage in providing up to date vulnerability information for NVD data consumers. The results from these APIs are updated as quickly as our website (unlike the traditional feeds which have explicit update intervals).

A few of the greater benefits of the APIs over the traditional data feeds are listed below:

• Retain all search capabilities based on the Advanced search page for the website
• Both CVE and CPE based searching capabilities
• No longer required to download entire feed files for simple requests
• Ability to see what has changed since a given date
• Ease of identifying CPE matches to Applicability statements

JSON Feeds

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.

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 cpe_dictionary@nist.gov as those CPEs may need approved to the official CPE dictionary. This feed is updated once per day.

RSS Vulnerability Feeds

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 nvd@nist.gov . 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.

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, the data feeds should 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.

META Files

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:

The META file should be used to determine if a given feed has been updated since your last import. This helps prevent unnecessary downloads of the .zip or .gz files and should result in a reasonable use of less than 200 requests per day.