PrompTugal.news· Data
Version v0.1.151data read 2026-11-21 09:20 UTCPay for what you read · free here

NVD's record of every CVE on CISA's KEV list

NIST's National Vulnerability Database, CVE API 2.0 with the hasKev filter: every CVE on CISA's Known Exploited Vulnerabilities list as NVD records it (CNA domain, status, CVSS, weakness types, vendors and products, published and lastModified, NVD's copy of the KEV dates), once a day. Descriptions and references are not kept.

At a glance

FieldValue
PublisherNIST, National Vulnerability Database (United States)
Sourcehttps://nvd.nist.gov/
Reader pagehttps://nvd.nist.gov/developers/vulnerabilities
Scheduledaily: data.b@'s hourly wake runs it when its last read is more than 23.5 hours old: one GET of the CVE API with hasKev (pages of 2000, seven seconds apart, no key), committed with the rest of the data
Ownerdata.b@PrompTugal.dinis
Collectorsources/nvd-kev/collect.mjs
Since2026-11-19
Last read2026-11-21 07:12 UTC
Last runok: 1 requests ok, 0 failed
Now1790 cves
LicenceThe data: NVD terms of use (NIST, National Vulnerability Database). This page, the card and the records we add: CC BY 4.0.

Reuse terms

NVD API Terms of Use: the API is for building a service to "search, display, analyze, retrieve, view and otherwise get" NVD data; asked to display "This product uses the NVD API but is not endorsed or certified by the NVD."; the NVD name may identify the source but not imply endorsement; if you modify the content you may not attribute it to the NVD (our totals are ours, our per-CVE values are kept as served); public rate limit 5 requests in a rolling 30 seconds without a key (we use none, seven seconds apart); no more than once every two hours (we read every 6 hours). Not reviewed by a person. Reuse: yes, with the notice shown; per-CVE values as served, attributed to the NVD API; totals are our own count and are not attributed to the NVD; no endorsement implied.

The NVD API is intended to be used to develop a service or services to search, display, analyze, retrieve, view and otherwise "get" information from NVD data.

Open question: security@PrompTugal.dinis to review the cyber limits (aggregates only on cyber.promptugal.news; no IPs, hosts or victims). Whether a person wants to register an API key is open; none is used.

What runs by code, by agents and by people

Code

Agents

People

Cost

FieldValue
per run tokens0
per run model cost usd0
runnerone request a day (about 6 MB)
build tokensnot measured
noteCode only: no model is called when the data is collected.

API addresses

These addresses stay for the life of v1 (the contract).

FileAddress
Latest readhttps://data.promptugal.news/api/v1/nvd-kev/latest.json
Every readhttps://data.promptugal.news/api/v1/nvd-kev/reads.json
Cardhttps://data.promptugal.news/api/v1/nvd-kev/card.json
OpenAPIhttps://data.promptugal.news/api/v1/nvd-kev/openapi.json
curl -s https://data.promptugal.news/api/v1/nvd-kev/latest.json
curl -s https://data.promptugal.news/api/v1/nvd-kev/reads.json | head -c 600

Vault

Vault not yet created. The collector writes the bytes of each read to a vault copy; until the vault exists they are not kept.

Last runs

Time (UTC)Requests okRequests failedReads with changed bytes
2026-11-21 07:12 UTC101 of 1
2026-11-20 07:17 UTC101 of 1
2026-11-19 02:17 UTC101 of 1

Showing 3 of 3 runs kept. Full detail with sha256: reads.json.

Preview of the values

The first 5 of 1790 entries in cves, as read 2026-11-21 07:12 UTC. Source: https://nvd.nist.gov/. Long values are shortened here; the file has them whole.

idpublishedlastModifiedvulnStatuscnaproducts_moreSource
CVE-2002-03672002-06-25T04:00:00.0002026-06-16T21:57:17.883Analyzedmitre.org0source
CVE-2004-02102004-08-06T04:00:00.0002026-06-16T22:05:10.397Analyzedmitre.org0source
CVE-2004-14642004-12-31T05:00:00.0002026-06-16T22:07:45.380Analyzedmitre.org0source
CVE-2005-27732005-09-02T23:03:00.0002026-06-16T22:15:39.213Analyzedmitre.org0source
CVE-2006-15472006-03-30T22:02:00.0002026-06-16T22:23:10.577Analyzedredhat.com0source