NVD Data Feeds

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

The 2.0 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

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.

META Files

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/.json 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-2.0-modified.json then the .meta file name will be nvdcve-2.0-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:

JSON 2.0 Feeds

These data feeds include updated NVD data in the new 2.0 JSON format. The "year" feeds are updated once per day, while the "recent" and "modified" feeds are updated every two hours.

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 [email protected] . 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.