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-07-03 18:03:51 +00:00
2025-07-03T18:00:13.002492+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-07-03 18:03:51 +00:00
2025-07-03T17:49:34+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-07-03 02:03:48 +00:00
2025-07-03T00:00:02.115490+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-07-03 18:03:51 +00:00
300234
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-07-03 18:03:51 +00:00
Recently added CVEs: `12`
2025-07-03 16:03:49 +00:00
2025-07-03 18:03:51 +00:00
- [CVE-2025-48939 ](CVE-2025/CVE-2025-489xx/CVE-2025-48939.json ) (`2025-07-03T17:15:39.300` )
- [CVE-2025-49846 ](CVE-2025/CVE-2025-498xx/CVE-2025-49846.json ) (`2025-07-03T17:15:39.613` )
- [CVE-2025-53489 ](CVE-2025/CVE-2025-534xx/CVE-2025-53489.json ) (`2025-07-03T17:15:39.850` )
- [CVE-2025-53490 ](CVE-2025/CVE-2025-534xx/CVE-2025-53490.json ) (`2025-07-03T16:15:23.823` )
- [CVE-2025-53500 ](CVE-2025/CVE-2025-535xx/CVE-2025-53500.json ) (`2025-07-03T17:15:39.990` )
- [CVE-2025-53501 ](CVE-2025/CVE-2025-535xx/CVE-2025-53501.json ) (`2025-07-03T17:15:40.127` )
- [CVE-2025-53502 ](CVE-2025/CVE-2025-535xx/CVE-2025-53502.json ) (`2025-07-03T17:15:40.250` )
- [CVE-2025-6071 ](CVE-2025/CVE-2025-60xx/CVE-2025-6071.json ) (`2025-07-03T17:15:40.373` )
- [CVE-2025-6072 ](CVE-2025/CVE-2025-60xx/CVE-2025-6072.json ) (`2025-07-03T17:15:40.567` )
- [CVE-2025-6073 ](CVE-2025/CVE-2025-60xx/CVE-2025-6073.json ) (`2025-07-03T17:15:40.750` )
- [CVE-2025-6074 ](CVE-2025/CVE-2025-60xx/CVE-2025-6074.json ) (`2025-07-03T17:15:40.920` )
- [CVE-2025-6926 ](CVE-2025/CVE-2025-69xx/CVE-2025-6926.json ) (`2025-07-03T17:15:41.100` )
2025-06-05 23:58:58 +00:00
2025-06-10 04:03:55 +00:00
2025-06-18 14:04:05 +00:00
### CVEs modified in the last Commit
2025-06-17 23:58:55 +00:00
2025-07-03 18:03:51 +00:00
Recently modified CVEs: `50`
- [CVE-2025-32073 ](CVE-2025/CVE-2025-320xx/CVE-2025-32073.json ) (`2025-07-03T17:15:38.940` )
- [CVE-2025-32074 ](CVE-2025/CVE-2025-320xx/CVE-2025-32074.json ) (`2025-07-03T17:15:39.067` )
- [CVE-2025-32079 ](CVE-2025/CVE-2025-320xx/CVE-2025-32079.json ) (`2025-07-03T17:15:39.183` )
- [CVE-2025-3863 ](CVE-2025/CVE-2025-38xx/CVE-2025-3863.json ) (`2025-07-03T17:09:19.293` )
- [CVE-2025-4584 ](CVE-2025/CVE-2025-45xx/CVE-2025-4584.json ) (`2025-07-03T17:38:28.387` )
- [CVE-2025-4585 ](CVE-2025/CVE-2025-45xx/CVE-2025-4585.json ) (`2025-07-03T17:49:34.000` )
- [CVE-2025-4586 ](CVE-2025/CVE-2025-45xx/CVE-2025-4586.json ) (`2025-07-03T17:39:43.090` )
- [CVE-2025-52969 ](CVE-2025/CVE-2025-529xx/CVE-2025-52969.json ) (`2025-07-03T16:15:23.710` )
- [CVE-2025-53492 ](CVE-2025/CVE-2025-534xx/CVE-2025-53492.json ) (`2025-07-03T16:15:23.957` )
- [CVE-2025-53493 ](CVE-2025/CVE-2025-534xx/CVE-2025-53493.json ) (`2025-07-03T16:15:24.123` )
- [CVE-2025-5526 ](CVE-2025/CVE-2025-55xx/CVE-2025-5526.json ) (`2025-07-03T16:56:52.057` )
- [CVE-2025-6191 ](CVE-2025/CVE-2025-61xx/CVE-2025-6191.json ) (`2025-07-03T16:12:00.510` )
- [CVE-2025-6192 ](CVE-2025/CVE-2025-61xx/CVE-2025-6192.json ) (`2025-07-03T16:12:12.790` )
- [CVE-2025-6425 ](CVE-2025/CVE-2025-64xx/CVE-2025-6425.json ) (`2025-07-03T16:23:06.293` )
- [CVE-2025-6426 ](CVE-2025/CVE-2025-64xx/CVE-2025-6426.json ) (`2025-07-03T16:25:12.367` )
- [CVE-2025-6427 ](CVE-2025/CVE-2025-64xx/CVE-2025-6427.json ) (`2025-07-03T16:37:00.490` )
- [CVE-2025-6428 ](CVE-2025/CVE-2025-64xx/CVE-2025-6428.json ) (`2025-07-03T16:42:54.900` )
- [CVE-2025-6429 ](CVE-2025/CVE-2025-64xx/CVE-2025-6429.json ) (`2025-07-03T16:43:05.600` )
- [CVE-2025-6430 ](CVE-2025/CVE-2025-64xx/CVE-2025-6430.json ) (`2025-07-03T16:43:15.240` )
- [CVE-2025-6431 ](CVE-2025/CVE-2025-64xx/CVE-2025-6431.json ) (`2025-07-03T16:04:21.163` )
- [CVE-2025-6432 ](CVE-2025/CVE-2025-64xx/CVE-2025-6432.json ) (`2025-07-03T16:04:29.550` )
- [CVE-2025-6433 ](CVE-2025/CVE-2025-64xx/CVE-2025-6433.json ) (`2025-07-03T16:04:41.260` )
- [CVE-2025-6434 ](CVE-2025/CVE-2025-64xx/CVE-2025-6434.json ) (`2025-07-03T16:04:52.800` )
- [CVE-2025-6435 ](CVE-2025/CVE-2025-64xx/CVE-2025-6435.json ) (`2025-07-03T16:09:39.497` )
- [CVE-2025-6436 ](CVE-2025/CVE-2025-64xx/CVE-2025-6436.json ) (`2025-07-03T16:09:47.610` )
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
2025-04-22 10:03:51 +00:00
This project uses and redistributes data from the NVD API but is not endorsed or certified by the NVD.
## Bot Source Code
The bot's source code is available at [fkie-cad/nvd\_json\_bot ](https://github.com/fkie-cad/nvd_json_bot ).