mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-05-06 18:52:58 +00:00
216 lines
8.8 KiB
Markdown
216 lines
8.8 KiB
Markdown
# nvd-json-data-feeds
|
|
|
|
[](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.
|
|
[Releases](https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest) each day at 00:00 AM UTC.
|
|
Repository synchronizes with the NVD every 2 hours.
|
|
|
|
## Repository at a Glance
|
|
|
|
### Last Repository Update
|
|
|
|
```plain
|
|
2025-04-10T10:00:19.447940+00:00
|
|
```
|
|
|
|
### Most recent CVE Modification Timestamp synchronized with NVD
|
|
|
|
```plain
|
|
2025-04-10T09:15:16.237000+00:00
|
|
```
|
|
|
|
### Last Data Feed Release
|
|
|
|
Download and Changelog: [Click](https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest)
|
|
|
|
```plain
|
|
2025-04-10T00:00:04.506020+00:00
|
|
```
|
|
|
|
### Total Number of included CVEs
|
|
|
|
```plain
|
|
289514
|
|
```
|
|
|
|
### CVEs added in the last Commit
|
|
|
|
Recently added CVEs: `44`
|
|
|
|
- [CVE-2025-32205](CVE-2025/CVE-2025-322xx/CVE-2025-32205.json) (`2025-04-10T08:15:17.490`)
|
|
- [CVE-2025-32206](CVE-2025/CVE-2025-322xx/CVE-2025-32206.json) (`2025-04-10T08:15:17.660`)
|
|
- [CVE-2025-32208](CVE-2025/CVE-2025-322xx/CVE-2025-32208.json) (`2025-04-10T08:15:17.813`)
|
|
- [CVE-2025-32209](CVE-2025/CVE-2025-322xx/CVE-2025-32209.json) (`2025-04-10T08:15:17.983`)
|
|
- [CVE-2025-32210](CVE-2025/CVE-2025-322xx/CVE-2025-32210.json) (`2025-04-10T08:15:18.143`)
|
|
- [CVE-2025-32212](CVE-2025/CVE-2025-322xx/CVE-2025-32212.json) (`2025-04-10T08:15:18.303`)
|
|
- [CVE-2025-32213](CVE-2025/CVE-2025-322xx/CVE-2025-32213.json) (`2025-04-10T08:15:18.473`)
|
|
- [CVE-2025-32214](CVE-2025/CVE-2025-322xx/CVE-2025-32214.json) (`2025-04-10T08:15:18.647`)
|
|
- [CVE-2025-32215](CVE-2025/CVE-2025-322xx/CVE-2025-32215.json) (`2025-04-10T08:15:18.803`)
|
|
- [CVE-2025-32216](CVE-2025/CVE-2025-322xx/CVE-2025-32216.json) (`2025-04-10T08:15:18.967`)
|
|
- [CVE-2025-32221](CVE-2025/CVE-2025-322xx/CVE-2025-32221.json) (`2025-04-10T08:15:19.123`)
|
|
- [CVE-2025-32227](CVE-2025/CVE-2025-322xx/CVE-2025-32227.json) (`2025-04-10T08:15:19.280`)
|
|
- [CVE-2025-32228](CVE-2025/CVE-2025-322xx/CVE-2025-32228.json) (`2025-04-10T08:15:19.437`)
|
|
- [CVE-2025-32230](CVE-2025/CVE-2025-322xx/CVE-2025-32230.json) (`2025-04-10T08:15:19.603`)
|
|
- [CVE-2025-32236](CVE-2025/CVE-2025-322xx/CVE-2025-32236.json) (`2025-04-10T08:15:19.760`)
|
|
- [CVE-2025-32240](CVE-2025/CVE-2025-322xx/CVE-2025-32240.json) (`2025-04-10T08:15:19.920`)
|
|
- [CVE-2025-32242](CVE-2025/CVE-2025-322xx/CVE-2025-32242.json) (`2025-04-10T08:15:20.080`)
|
|
- [CVE-2025-32243](CVE-2025/CVE-2025-322xx/CVE-2025-32243.json) (`2025-04-10T08:15:20.237`)
|
|
- [CVE-2025-32244](CVE-2025/CVE-2025-322xx/CVE-2025-32244.json) (`2025-04-10T08:15:20.387`)
|
|
- [CVE-2025-32259](CVE-2025/CVE-2025-322xx/CVE-2025-32259.json) (`2025-04-10T08:15:20.540`)
|
|
- [CVE-2025-32260](CVE-2025/CVE-2025-322xx/CVE-2025-32260.json) (`2025-04-10T08:15:20.693`)
|
|
- [CVE-2025-32275](CVE-2025/CVE-2025-322xx/CVE-2025-32275.json) (`2025-04-10T08:15:20.847`)
|
|
- [CVE-2025-32282](CVE-2025/CVE-2025-322xx/CVE-2025-32282.json) (`2025-04-10T08:15:21.020`)
|
|
- [CVE-2025-32668](CVE-2025/CVE-2025-326xx/CVE-2025-32668.json) (`2025-04-10T08:15:21.190`)
|
|
- [CVE-2025-32687](CVE-2025/CVE-2025-326xx/CVE-2025-32687.json) (`2025-04-10T08:15:21.350`)
|
|
|
|
|
|
### CVEs modified in the last Commit
|
|
|
|
Recently modified CVEs: `1`
|
|
|
|
- [CVE-2025-30280](CVE-2025/CVE-2025-302xx/CVE-2025-30280.json) (`2025-04-10T09:15:16.237`)
|
|
|
|
|
|
## Download and Usage
|
|
|
|
There are several ways you can work with the data in this repository:
|
|
|
|
### 1) Release Data Feed Packages
|
|
|
|
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).
|
|
|
|
Each day at 00:00 AM UTC we package and upload JSON files that aim to reconstruct the legacy NVD CVE Data Feeds.
|
|
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
|
|
CVE-2024.json
|
|
```
|
|
|
|
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.
|
|
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:
|
|
|
|
```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
|
|
```
|
|
|
|
Note that all feeds are distributed in `xz`-compressed format to save storage and bandwidth.
|
|
For decompression execute:
|
|
|
|
```sh
|
|
xz -d -k <feed>.json.xz
|
|
```
|
|
|
|
#### Automation using Release Data Feed Packages
|
|
|
|
You can fetch the latest releases for each package with the following static link layout:
|
|
|
|
```sh
|
|
https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest/download/CVE-<YEAR>.json.xz
|
|
```
|
|
|
|
Example:
|
|
|
|
```sh
|
|
wget https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest/download/CVE-2024.json.xz
|
|
xz -d -k CVE-2024.json.xz
|
|
```
|
|
|
|
### 2) Clone the Repository (with Git History)
|
|
|
|
As you can see by browsing this repository, there is a slight difference between the release packages format and the repository folder structure.
|
|
This is because we want to maintain explorability of the dataset.
|
|
|
|
Each CVE gets its own JSON file, e.g., `CVE-1999-0001.json`.
|
|
Here, each file is put into a folder layout that first sorts by CVE `year` identifier part and then by `number` part.
|
|
We mask (`xx`) the last two digits to create easily navigable folders that hold a maximum of 100 CVE JSON files:
|
|
|
|
```plain
|
|
.
|
|
├── CVE-1999
|
|
│ ├── CVE-1999-00xx
|
|
│ │ ├── CVE-1999-0001.json
|
|
│ │ ├── CVE-1999-0002.json
|
|
│ │ └── [...]
|
|
│ ├── CVE-1999-01xx
|
|
│ │ ├── CVE-1999-0101.json
|
|
│ │ └── [...]
|
|
│ └── [...]
|
|
├── CVE-2000
|
|
│ ├── CVE-2000-00xx
|
|
│ ├── CVE-2000-01xx
|
|
│ └── [...]
|
|
└── [...]
|
|
```
|
|
|
|
A byproduct of managing and continuously updating this dataset via Git is that we can track changes over time through the Git history.
|
|
|
|
If you are interested in having the NVD data as organized above, including the historical data of changes, just clone this repository (large!):
|
|
|
|
```sh
|
|
git clone https://github.com/fkie-cad/nvd-json-data-feeds.git
|
|
```
|
|
|
|
#### (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
|
|
```
|
|
|
|
### 3) Clone the Repository (without Git History)
|
|
|
|
Don't need the history? Then create a shallow copy:
|
|
|
|
```sh
|
|
git clone --depth 1 -b main https://github.com/fkie-cad/nvd-json-data-feeds.git
|
|
```
|
|
|
|
|
|
## Update Timetable
|
|
|
|
* NVD Synchronization: `Bi-Hourly`, starting with `00:00:00Z`
|
|
* Release Packages: `Daily`, at `00:00:00Z`
|
|
* NVD Rebuilds: `Weekly`, at `Sun, 02:30:00Z`
|
|
|
|
|
|
## Motivation
|
|
|
|
On 2023-12-15, the NIST deprecated all [JSON-based NVD Data Feeds](https://nvd.nist.gov/vuln/data-feeds#divRetirementBanner-1).
|
|
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.:
|
|
|
|
- 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`!
|
|
|
|
Unfortunately, the new NVD API 2.0 adds complexity to this process.
|
|
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. |