2023-04-27 15:02:47 +02:00
# nvd-json-data-feeds
2023-04-24 14:55:30 +02:00
2024-03-26 17:03:58 +00:00
[](https://github.com/fkie-cad/nvd-json-data-feeds/actions/workflows/monitor_release.yml)
[](https://github.com/fkie-cad/nvd-json-data-feeds/actions/workflows/monitor_sync.yml)
[](https://github.com/fkie-cad/nvd-json-data-feeds/actions/workflows/validate_schema.yml)
Community reconstruction of the deprecated JSON NVD Data Feeds.
2023-05-17 08:57:59 +00:00
[Releases ](https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest ) each day at 00:00 AM UTC.
2023-04-27 16:00:24 +02:00
Repository synchronizes with the NVD every 2 hours.
2023-04-24 14:55:30 +02:00
2023-04-27 16:00:24 +02:00
## Repository at a Glance
2023-04-24 14:55:30 +02:00
2023-04-27 16:00:24 +02:00
### Last Repository Update
2023-04-24 14:55:30 +02:00
```plain
2025-02-12 15:05:16 +00:00
2025-02-12T15:01:51.308621+00:00
2023-04-24 14:55:30 +02:00
```
2023-04-27 16:00:24 +02:00
### Most recent CVE Modification Timestamp synchronized with NVD
2023-04-24 14:55:30 +02:00
```plain
2025-02-12 15:05:16 +00:00
2025-02-12T14:59:58.097000+00:00
2023-04-24 14:55:30 +02:00
```
2023-04-27 16:00:24 +02:00
### Last Data Feed Release
2023-04-24 14:55:30 +02:00
2023-05-17 08:57:59 +00:00
Download and Changelog: [Click ](https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest )
2023-04-24 14:55:30 +02:00
```plain
2025-02-12 03:04:24 +00:00
2025-02-12T01:00:04.376896+00:00
2023-04-24 14:55:30 +02:00
```
2023-04-27 16:00:24 +02:00
### Total Number of included CVEs
2023-04-24 14:55:30 +02:00
2023-04-27 15:02:47 +02:00
```plain
2025-02-12 15:05:16 +00:00
281043
2023-04-24 14:55:30 +02:00
```
2023-04-27 16:00:24 +02:00
### CVEs added in the last Commit
2023-04-24 14:55:30 +02:00
2025-02-12 15:05:16 +00:00
Recently added CVEs: `57`
- [CVE-2025-26354 ](CVE-2025/CVE-2025-263xx/CVE-2025-26354.json ) (`2025-02-12T14:15:35.727` )
- [CVE-2025-26355 ](CVE-2025/CVE-2025-263xx/CVE-2025-26355.json ) (`2025-02-12T14:15:35.870` )
- [CVE-2025-26356 ](CVE-2025/CVE-2025-263xx/CVE-2025-26356.json ) (`2025-02-12T14:15:36.017` )
- [CVE-2025-26357 ](CVE-2025/CVE-2025-263xx/CVE-2025-26357.json ) (`2025-02-12T14:15:36.160` )
- [CVE-2025-26358 ](CVE-2025/CVE-2025-263xx/CVE-2025-26358.json ) (`2025-02-12T14:15:36.297` )
- [CVE-2025-26359 ](CVE-2025/CVE-2025-263xx/CVE-2025-26359.json ) (`2025-02-12T14:15:36.437` )
- [CVE-2025-26360 ](CVE-2025/CVE-2025-263xx/CVE-2025-26360.json ) (`2025-02-12T14:15:36.577` )
- [CVE-2025-26361 ](CVE-2025/CVE-2025-263xx/CVE-2025-26361.json ) (`2025-02-12T14:15:36.717` )
- [CVE-2025-26362 ](CVE-2025/CVE-2025-263xx/CVE-2025-26362.json ) (`2025-02-12T14:15:36.847` )
- [CVE-2025-26363 ](CVE-2025/CVE-2025-263xx/CVE-2025-26363.json ) (`2025-02-12T14:15:36.983` )
- [CVE-2025-26364 ](CVE-2025/CVE-2025-263xx/CVE-2025-26364.json ) (`2025-02-12T14:15:37.123` )
- [CVE-2025-26365 ](CVE-2025/CVE-2025-263xx/CVE-2025-26365.json ) (`2025-02-12T14:15:37.267` )
- [CVE-2025-26366 ](CVE-2025/CVE-2025-263xx/CVE-2025-26366.json ) (`2025-02-12T14:15:37.397` )
- [CVE-2025-26367 ](CVE-2025/CVE-2025-263xx/CVE-2025-26367.json ) (`2025-02-12T14:15:37.533` )
- [CVE-2025-26368 ](CVE-2025/CVE-2025-263xx/CVE-2025-26368.json ) (`2025-02-12T14:15:37.660` )
- [CVE-2025-26369 ](CVE-2025/CVE-2025-263xx/CVE-2025-26369.json ) (`2025-02-12T14:15:37.800` )
- [CVE-2025-26370 ](CVE-2025/CVE-2025-263xx/CVE-2025-26370.json ) (`2025-02-12T14:15:37.940` )
- [CVE-2025-26371 ](CVE-2025/CVE-2025-263xx/CVE-2025-26371.json ) (`2025-02-12T14:15:38.077` )
- [CVE-2025-26372 ](CVE-2025/CVE-2025-263xx/CVE-2025-26372.json ) (`2025-02-12T14:15:38.227` )
- [CVE-2025-26373 ](CVE-2025/CVE-2025-263xx/CVE-2025-26373.json ) (`2025-02-12T14:15:38.360` )
- [CVE-2025-26374 ](CVE-2025/CVE-2025-263xx/CVE-2025-26374.json ) (`2025-02-12T14:15:38.500` )
- [CVE-2025-26375 ](CVE-2025/CVE-2025-263xx/CVE-2025-26375.json ) (`2025-02-12T14:15:38.633` )
- [CVE-2025-26376 ](CVE-2025/CVE-2025-263xx/CVE-2025-26376.json ) (`2025-02-12T14:15:38.777` )
- [CVE-2025-26377 ](CVE-2025/CVE-2025-263xx/CVE-2025-26377.json ) (`2025-02-12T14:15:38.933` )
- [CVE-2025-26378 ](CVE-2025/CVE-2025-263xx/CVE-2025-26378.json ) (`2025-02-12T14:15:39.163` )
2025-01-31 00:59:38 +00:00
2025-01-31 05:03:59 +00:00
2025-02-12 03:04:24 +00:00
### CVEs modified in the last Commit
2025-02-12 01:00:14 +00:00
2025-02-12 15:05:16 +00:00
Recently modified CVEs: `20`
- [CVE-2022-23439 ](CVE-2022/CVE-2022-234xx/CVE-2022-23439.json ) (`2025-02-12T13:39:42.107` )
- [CVE-2024-21890 ](CVE-2024/CVE-2024-218xx/CVE-2024-21890.json ) (`2025-02-12T14:59:58.097` )
- [CVE-2025-20881 ](CVE-2025/CVE-2025-208xx/CVE-2025-20881.json ) (`2025-02-12T13:42:58.443` )
- [CVE-2025-20882 ](CVE-2025/CVE-2025-208xx/CVE-2025-20882.json ) (`2025-02-12T13:43:13.267` )
- [CVE-2025-20883 ](CVE-2025/CVE-2025-208xx/CVE-2025-20883.json ) (`2025-02-12T13:43:37.743` )
- [CVE-2025-20884 ](CVE-2025/CVE-2025-208xx/CVE-2025-20884.json ) (`2025-02-12T13:44:06.350` )
- [CVE-2025-20885 ](CVE-2025/CVE-2025-208xx/CVE-2025-20885.json ) (`2025-02-12T13:45:19.913` )
- [CVE-2025-20886 ](CVE-2025/CVE-2025-208xx/CVE-2025-20886.json ) (`2025-02-12T13:45:48.443` )
- [CVE-2025-20887 ](CVE-2025/CVE-2025-208xx/CVE-2025-20887.json ) (`2025-02-12T13:46:17.187` )
- [CVE-2025-20888 ](CVE-2025/CVE-2025-208xx/CVE-2025-20888.json ) (`2025-02-12T13:46:35.857` )
- [CVE-2025-20889 ](CVE-2025/CVE-2025-208xx/CVE-2025-20889.json ) (`2025-02-12T13:46:49.193` )
- [CVE-2025-20890 ](CVE-2025/CVE-2025-208xx/CVE-2025-20890.json ) (`2025-02-12T13:47:05.413` )
- [CVE-2025-20891 ](CVE-2025/CVE-2025-208xx/CVE-2025-20891.json ) (`2025-02-12T13:47:21.220` )
- [CVE-2025-20892 ](CVE-2025/CVE-2025-208xx/CVE-2025-20892.json ) (`2025-02-12T13:47:40.283` )
- [CVE-2025-20893 ](CVE-2025/CVE-2025-208xx/CVE-2025-20893.json ) (`2025-02-12T13:48:39.090` )
- [CVE-2025-20904 ](CVE-2025/CVE-2025-209xx/CVE-2025-20904.json ) (`2025-02-12T13:48:47.607` )
- [CVE-2025-20905 ](CVE-2025/CVE-2025-209xx/CVE-2025-20905.json ) (`2025-02-12T13:49:26.310` )
- [CVE-2025-20907 ](CVE-2025/CVE-2025-209xx/CVE-2025-20907.json ) (`2025-02-12T13:49:49.460` )
- [CVE-2025-21135 ](CVE-2025/CVE-2025-211xx/CVE-2025-21135.json ) (`2025-02-12T13:38:26.103` )
- [CVE-2025-22936 ](CVE-2025/CVE-2025-229xx/CVE-2025-22936.json ) (`2025-02-12T14:15:33.187` )
2023-04-24 14:55:30 +02:00
## Download and Usage
There are several ways you can work with the data in this repository:
### 1) Release Data Feed Packages
2023-05-24 12:00:30 +00:00
The most straightforward approach is to obtain the latest Data Feed release packages [here ](https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest ).
2023-04-24 14:55:30 +02:00
2023-04-27 16:00:24 +02:00
Each day at 00:00 AM UTC we package and upload JSON files that aim to reconstruct the legacy NVD CVE Data Feeds.
2023-04-24 14:55:30 +02:00
Those are aggregated by the `year` part of the CVE identifier:
```
# CVE-<YEAR>.json
CVE-1999.json
CVE-2001.json
CVE-2002.json
CVE-2003.json
[...]
CVE-2023.json
2024-04-04 10:03:21 +00:00
CVE-2024.json
2023-04-24 14:55:30 +02:00
```
2023-04-27 15:02:47 +02:00
We also upload the well-known `Recent` and `Modified` feeds.
Furthermore, we provide the `All` feed, which contains a recent snapshot of all NVD records.
2023-04-27 16:00:24 +02:00
Once your local copy is synchronized and the last synchronization is no older than 8 days, you can rely on these to stay up to date:
2023-04-24 14:55:30 +02:00
```plain
CVE-Recent.json # CVEs that were added in the previous eight days
CVE-Modified.json # CVEs that were modified or added in the previous eight days
```
2023-04-27 16:00:24 +02:00
Note that all feeds are distributed in `xz` -compressed format to save storage and bandwidth.
2023-04-24 14:55:30 +02:00
For decompression execute:
```sh
xz -d -k < feed > .json.xz
```
#### Automation using Release Data Feed Packages
2023-04-27 16:00:24 +02:00
You can fetch the latest releases for each package with the following static link layout:
2023-04-24 14:55:30 +02:00
```sh
2023-04-27 15:02:47 +02:00
https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest/download/CVE-< YEAR > .json.xz
2023-04-24 14:55:30 +02:00
```
Example:
```sh
2024-04-04 10:03:21 +00:00
wget https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest/download/CVE-2024.json.xz
xz -d -k CVE-2024.json.xz
2023-04-24 14:55:30 +02:00
```
2023-04-27 16:00:24 +02:00
### 2) Clone the Repository (with Git History)
2023-04-24 14:55:30 +02:00
2023-04-27 16:00:24 +02:00
As you can see by browsing this repository, there is a slight difference between the release packages format and the repository folder structure.
2023-04-24 14:55:30 +02:00
This is because we want to maintain explorability of the dataset.
2023-04-27 16:00:24 +02:00
Each CVE gets its own JSON file, e.g., `CVE-1999-0001.json` .
2023-04-24 14:55:30 +02:00
Here, each file is put into a folder layout that first sorts by CVE `year` identifier part and then by `number` part.
2023-04-27 16:00:24 +02:00
We mask (`xx` ) the last two digits to create easily navigable folders that hold a maximum of 100 CVE JSON files:
2023-04-24 14:55:30 +02:00
```plain
.
├── CVE-1999
│ ├── CVE-1999-00xx
│ │ ├── CVE-1999-0001.json
│ │ ├── CVE-1999-0002.json
│ │ └── [...]
│ ├── CVE-1999-01xx
2023-04-25 17:08:25 +02:00
│ │ ├── CVE-1999-0101.json
│ │ └── [...]
2023-04-24 14:55:30 +02:00
│ └── [...]
├── CVE-2000
│ ├── CVE-2000-00xx
│ ├── CVE-2000-01xx
│ └── [...]
└── [...]
```
2023-04-27 16:00:24 +02:00
A byproduct of managing and continuously updating this dataset via Git is that we can track changes over time through the Git history.
2023-04-24 14:55:30 +02:00
2023-04-27 16:00:24 +02:00
If you are interested in having the NVD data as organized above, including the historical data of changes, just clone this repository (large!):
2023-04-24 14:55:30 +02:00
```sh
2023-04-27 15:02:47 +02:00
git clone https://github.com/fkie-cad/nvd-json-data-feeds.git
2023-04-24 14:55:30 +02:00
```
2023-12-21 15:00:28 +00:00
#### (Optional) Meta Files
Similar to the old official feeds, we provide meta files with each release. They can be fetched for each feed via:
```sh
https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest/download/CVE-< YEAR > .meta
```
The structure is as follows:
```plain
lastModifiedDate:1970-01-01T00:00:00.000+00:00 # ISO 8601 timestamp of last CVE modification
size:1000 # size of uncompressed feed (bytes)
xzSize:100 # size of lzma-compressed feed (bytes)
sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 # sha256 hexdigest of uncompressed feed
```
2023-04-27 16:00:24 +02:00
### 3) Clone the Repository (without Git History)
2023-04-24 14:55:30 +02:00
Don't need the history? Then create a shallow copy:
```sh
2023-04-27 15:02:47 +02:00
git clone --depth 1 -b main https://github.com/fkie-cad/nvd-json-data-feeds.git
2023-04-24 14:55:30 +02:00
```
2024-04-04 10:03:21 +00:00
## Update Timetable
* NVD Synchronization: `Bi-Hourly` , starting with `00:00:00Z`
2024-04-04 12:03:25 +00:00
* Release Packages: `Daily` , at `00:00:00Z`
2024-04-04 10:03:21 +00:00
* NVD Rebuilds: `Weekly` , at `Sun, 02:30:00Z`
2023-04-24 14:55:30 +02:00
## Motivation
2023-12-15 13:00:27 +00:00
On 2023-12-15, the NIST deprecated all [JSON-based NVD Data Feeds ](https://nvd.nist.gov/vuln/data-feeds#divRetirementBanner-1 ).
2023-04-24 14:55:30 +02:00
The new [NVD CVE API 2.0 ](https://nvd.nist.gov/developers/vulnerabilities ) is, without a doubt, a great way to obtain CVE information.
However, we from [Fraunhofer FKIE - Cyber Analysis and Defense ](https://www.fkie.fraunhofer.de/en/departments/cad.html ) believe that the API does not cover a variety of use cases.
The legacy NVD Data Feeds provided a convenient way to quickly obtain a complete, file-based offline database snapshot; just download the `CVE-<YEAR>.tar.gz` , decompress it, and use it as you please, e.g.:
2024-03-26 17:03:58 +00:00
- Put the JSON feed into a document-based database and quickly leverage upon that data in your software project, ...
- Parse and analyze it using your favorite programming language, ...
- Put it on a USB stick and transfer it to a system without internet access, or ...
- Query the file using `jq` !
2023-04-24 14:55:30 +02:00
2023-04-27 16:00:24 +02:00
Unfortunately, the new NVD API 2.0 adds complexity to this process.
2023-04-24 14:55:30 +02:00
We want to preserve ease of use by reconstructing these data sources.
## Non-Endorsement Clause
This project uses and redistributes data from the NVD API but is not endorsed or certified by the NVD.