mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-07-11 16:13:34 +00:00
244 lines
11 KiB
Markdown
244 lines
11 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-07-08T16:00:11.703697+00:00
|
|
```
|
|
|
|
### Most recent CVE Modification Timestamp synchronized with NVD
|
|
|
|
```plain
|
|
2025-07-08T15:59:52.273000+00:00
|
|
```
|
|
|
|
### Last Data Feed Release
|
|
|
|
Download and Changelog: [Click](https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest)
|
|
|
|
```plain
|
|
2025-07-08T00:00:02.131304+00:00
|
|
```
|
|
|
|
### Total Number of included CVEs
|
|
|
|
```plain
|
|
300908
|
|
```
|
|
|
|
### CVEs added in the last Commit
|
|
|
|
Recently added CVEs: `25`
|
|
|
|
- [CVE-2024-52965](CVE-2024/CVE-2024-529xx/CVE-2024-52965.json) (`2025-07-08T15:15:22.313`)
|
|
- [CVE-2024-55599](CVE-2024/CVE-2024-555xx/CVE-2024-55599.json) (`2025-07-08T15:15:23.870`)
|
|
- [CVE-2025-24474](CVE-2025/CVE-2025-244xx/CVE-2025-24474.json) (`2025-07-08T15:15:26.220`)
|
|
- [CVE-2025-2793](CVE-2025/CVE-2025-27xx/CVE-2025-2793.json) (`2025-07-08T15:15:27.023`)
|
|
- [CVE-2025-2827](CVE-2025/CVE-2025-28xx/CVE-2025-2827.json) (`2025-07-08T15:15:27.190`)
|
|
- [CVE-2025-29267](CVE-2025/CVE-2025-292xx/CVE-2025-29267.json) (`2025-07-08T15:15:26.827`)
|
|
- [CVE-2025-3630](CVE-2025/CVE-2025-36xx/CVE-2025-3630.json) (`2025-07-08T15:15:27.560`)
|
|
- [CVE-2025-36600](CVE-2025/CVE-2025-366xx/CVE-2025-36600.json) (`2025-07-08T15:15:27.403`)
|
|
- [CVE-2025-47422](CVE-2025/CVE-2025-474xx/CVE-2025-47422.json) (`2025-07-08T14:15:27.997`)
|
|
- [CVE-2025-53372](CVE-2025/CVE-2025-533xx/CVE-2025-53372.json) (`2025-07-08T15:15:29.560`)
|
|
- [CVE-2025-53480](CVE-2025/CVE-2025-534xx/CVE-2025-53480.json) (`2025-07-08T15:15:29.720`)
|
|
- [CVE-2025-53545](CVE-2025/CVE-2025-535xx/CVE-2025-53545.json) (`2025-07-08T15:15:29.850`)
|
|
- [CVE-2025-5450](CVE-2025/CVE-2025-54xx/CVE-2025-5450.json) (`2025-07-08T15:15:31.103`)
|
|
- [CVE-2025-5451](CVE-2025/CVE-2025-54xx/CVE-2025-5451.json) (`2025-07-08T15:15:31.817`)
|
|
- [CVE-2025-5463](CVE-2025/CVE-2025-54xx/CVE-2025-5463.json) (`2025-07-08T15:15:32.010`)
|
|
- [CVE-2025-6770](CVE-2025/CVE-2025-67xx/CVE-2025-6770.json) (`2025-07-08T15:15:33.287`)
|
|
- [CVE-2025-6995](CVE-2025/CVE-2025-69xx/CVE-2025-6995.json) (`2025-07-08T15:15:33.707`)
|
|
- [CVE-2025-6996](CVE-2025/CVE-2025-69xx/CVE-2025-6996.json) (`2025-07-08T15:15:33.860`)
|
|
- [CVE-2025-7037](CVE-2025/CVE-2025-70xx/CVE-2025-7037.json) (`2025-07-08T15:15:34.010`)
|
|
- [CVE-2025-7180](CVE-2025/CVE-2025-71xx/CVE-2025-7180.json) (`2025-07-08T14:15:31.970`)
|
|
- [CVE-2025-7181](CVE-2025/CVE-2025-71xx/CVE-2025-7181.json) (`2025-07-08T14:15:32.177`)
|
|
- [CVE-2025-7182](CVE-2025/CVE-2025-71xx/CVE-2025-7182.json) (`2025-07-08T15:15:34.230`)
|
|
- [CVE-2025-7183](CVE-2025/CVE-2025-71xx/CVE-2025-7183.json) (`2025-07-08T15:15:34.430`)
|
|
- [CVE-2025-7326](CVE-2025/CVE-2025-73xx/CVE-2025-7326.json) (`2025-07-08T15:15:34.623`)
|
|
- [CVE-2025-7345](CVE-2025/CVE-2025-73xx/CVE-2025-7345.json) (`2025-07-08T14:15:32.397`)
|
|
|
|
|
|
### CVEs modified in the last Commit
|
|
|
|
Recently modified CVEs: `137`
|
|
|
|
- [CVE-2025-6868](CVE-2025/CVE-2025-68xx/CVE-2025-6868.json) (`2025-07-08T14:37:18.003`)
|
|
- [CVE-2025-6881](CVE-2025/CVE-2025-68xx/CVE-2025-6881.json) (`2025-07-08T14:18:32.693`)
|
|
- [CVE-2025-6883](CVE-2025/CVE-2025-68xx/CVE-2025-6883.json) (`2025-07-08T14:18:19.600`)
|
|
- [CVE-2025-6884](CVE-2025/CVE-2025-68xx/CVE-2025-6884.json) (`2025-07-08T14:18:11.347`)
|
|
- [CVE-2025-6885](CVE-2025/CVE-2025-68xx/CVE-2025-6885.json) (`2025-07-08T14:17:03.797`)
|
|
- [CVE-2025-6888](CVE-2025/CVE-2025-68xx/CVE-2025-6888.json) (`2025-07-08T14:16:55.400`)
|
|
- [CVE-2025-6889](CVE-2025/CVE-2025-68xx/CVE-2025-6889.json) (`2025-07-08T14:16:47.070`)
|
|
- [CVE-2025-6890](CVE-2025/CVE-2025-68xx/CVE-2025-6890.json) (`2025-07-08T14:16:41.300`)
|
|
- [CVE-2025-6891](CVE-2025/CVE-2025-68xx/CVE-2025-6891.json) (`2025-07-08T14:16:33.023`)
|
|
- [CVE-2025-6901](CVE-2025/CVE-2025-69xx/CVE-2025-6901.json) (`2025-07-08T14:16:24.390`)
|
|
- [CVE-2025-6902](CVE-2025/CVE-2025-69xx/CVE-2025-6902.json) (`2025-07-08T14:16:12.293`)
|
|
- [CVE-2025-6908](CVE-2025/CVE-2025-69xx/CVE-2025-6908.json) (`2025-07-08T14:15:57.870`)
|
|
- [CVE-2025-6909](CVE-2025/CVE-2025-69xx/CVE-2025-6909.json) (`2025-07-08T14:15:29.440`)
|
|
- [CVE-2025-6910](CVE-2025/CVE-2025-69xx/CVE-2025-6910.json) (`2025-07-08T14:15:16.237`)
|
|
- [CVE-2025-6911](CVE-2025/CVE-2025-69xx/CVE-2025-6911.json) (`2025-07-08T14:15:05.867`)
|
|
- [CVE-2025-6912](CVE-2025/CVE-2025-69xx/CVE-2025-6912.json) (`2025-07-08T14:14:24.530`)
|
|
- [CVE-2025-6913](CVE-2025/CVE-2025-69xx/CVE-2025-6913.json) (`2025-07-08T14:14:13.950`)
|
|
- [CVE-2025-6914](CVE-2025/CVE-2025-69xx/CVE-2025-6914.json) (`2025-07-08T14:13:59.330`)
|
|
- [CVE-2025-6915](CVE-2025/CVE-2025-69xx/CVE-2025-6915.json) (`2025-07-08T14:52:37.427`)
|
|
- [CVE-2025-7053](CVE-2025/CVE-2025-70xx/CVE-2025-7053.json) (`2025-07-08T14:15:29.430`)
|
|
- [CVE-2025-7067](CVE-2025/CVE-2025-70xx/CVE-2025-7067.json) (`2025-07-08T14:15:29.597`)
|
|
- [CVE-2025-7068](CVE-2025/CVE-2025-70xx/CVE-2025-7068.json) (`2025-07-08T14:15:30.160`)
|
|
- [CVE-2025-7069](CVE-2025/CVE-2025-70xx/CVE-2025-7069.json) (`2025-07-08T14:15:30.420`)
|
|
- [CVE-2025-7070](CVE-2025/CVE-2025-70xx/CVE-2025-7070.json) (`2025-07-08T14:15:30.593`)
|
|
- [CVE-2025-7135](CVE-2025/CVE-2025-71xx/CVE-2025-7135.json) (`2025-07-08T14:15:30.760`)
|
|
|
|
|
|
## 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.
|
|
|
|
## Bot Source Code
|
|
|
|
The bot's source code is available at [fkie-cad/nvd\_json\_bot](https://github.com/fkie-cad/nvd_json_bot). |