CVEs published or modified in the last 24 hours (NVD)
NIST's National Vulnerability Database, CVE API 2.0: the CVEs published or modified in the 24 hours before each read, each with its CNA, status, CVSS base severity and score, weakness types and the vendors and products (NVD's CPE configurations, else the CNA's own list in the same record, marked); and totals per day and severity, for cyber.promptugal.news's pulse. Products only, never a victim, host or address. No descriptions or reference links are kept.
Three layers: the source (who publishes it, the terms, when it was read), the raw data as the publisher served it, and the processed data, what this site makes of it. The processing is where the value is: named fields, places joined, gaps marked, every value kept with its source and time.
1. The source
At a glance
| Field | Value |
|---|---|
| Publisher | NIST, National Vulnerability Database (United States) |
| Source | https://nvd.nist.gov/ |
| Reader page | https://nvd.nist.gov/developers/vulnerabilities |
| Schedule | every 6 hours: the Pages workflow (.github/workflows/pages.yml) at 17 minutes past 00, 06, 12 and 18 UTC; up to four GETs of the CVE API (pages of 2000 of the CVEs modified since 00:00 UTC yesterday, seven seconds apart, no key; the new CVEs are those published in the same window); every other run keeps the last read, copied from the live site |
| Owner | data.b@PrompTugal.dinis |
| Collector | sources/nvd-cve/collect.mjs |
| Since | 2026-11-18 |
| Last read | 2026-11-21 07:12 UTC |
| Last run | ok: 1 requests ok, 0 failed |
| Now | 1357 cves in window |
| Licence | The 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.
2. The raw data
The raw files are NVD's own CVE API answers (about 6 MB a page, with every description and reference), kept in the vault copy and not served here: the API. This product uses the NVD API but is not endorsed or certified by the NVD.
3. The processed data
The collector reads NVD's CVE API for the last 24 to 48 hours (no key, seven seconds between requests), keeps each CVE's identifier, dates, status, CNA, CVSS severity and score, weakness types and vendor and product (from NVD's CPE, else the CNA's own list), and counts per day, severity, CNA and vendor. The counts are ours; the values are NVD's as served. The result: latest.json.
CVEs NVD published and modified in the last 24 hours, by day and severity, and the CNAs and vendors with the most. The data: /api/v1/nvd-cve/latest.json.
More about this source
What runs by code, by agents and by people
Code
- the collector reads NVD's CVE API for the last 24 hours, keeps identifiers and classifications, and counts per day, severity, CNA and vendor
- GitHub Actions runs it and deploys the site
Agents
- data.b@PrompTugal.dinis wrote the collector and card on 18 November 2026, at cyber.b@PrompTugal.dinis's request; terms read the same day by data.b.dev@
People
- Dinis Cruz decided the cyber signals on 18 November 2026 (board/guidance/2026-11-18-people-blogs-cyber-and-simulated-payments.md); no person has checked the values (not reviewed)
Cost
| Field | Value |
|---|---|
| per run tokens | 0 |
| per run model cost usd | 0 |
| runner | GitHub Actions on a public repository: no charge; about four requests a run (about 6 MB each) |
| build tokens | not measured |
| note | Code only: no model is called when the data is collected. |
API addresses
These addresses stay for the life of v1 (the contract).
curl -s https://data.promptugal.news/api/v1/nvd-cve/latest.json
curl -s https://data.promptugal.news/api/v1/nvd-cve/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 ok | Requests failed | Reads with changed bytes |
|---|---|---|---|
| 2026-11-21 07:12 UTC | 1 | 0 | 1 of 1 |
| 2026-11-20 18:15 UTC | 2 | 0 | 2 of 2 |
| 2026-11-20 07:17 UTC | 2 | 0 | 2 of 2 |
| 2026-11-19 18:14 UTC | 2 | 0 | 2 of 2 |
| 2026-11-19 12:15 UTC | 2 | 0 | 2 of 2 |
| 2026-11-19 06:15 UTC | 1 | 0 | 1 of 1 |
| 2026-11-18 23:48 UTC | 2 | 0 | 2 of 2 |
| 2026-11-18 23:40 UTC | 2 | 0 | 2 of 2 |
| 2026-11-18 23:31 UTC | 2 | 0 | 2 of 2 |
| 2026-11-18 23:25 UTC | 2 | 0 | 2 of 2 |
| 2026-11-18 22:57 UTC | 2 | 0 | 2 of 2 |
| 2026-11-18 22:46 UTC | 2 | 0 | 2 of 2 |
| 2026-11-18 22:40 UTC | 2 | 0 | 2 of 2 |
| 2026-11-18 22:35 UTC | 2 | 0 | 2 of 2 |
| 2026-11-18 22:29 UTC | 2 | 0 | 2 of 2 |
| 2026-11-18 22:23 UTC | 2 | 0 | 2 of 2 |
| 2026-11-18 22:14 UTC | 3 | 0 | 3 of 3 |
| 2026-11-18 22:10 UTC | 3 | 0 | 3 of 3 |
| 2026-11-18 21:15 UTC | 3 | 0 | 3 of 3 |
Showing 19 of 19 runs kept. Full detail with sha256: reads.json.
Preview of the values
The first 2 of 2 entries in daily, as read 2026-11-21 07:12 UTC. Source: https://nvd.nist.gov/. Long values are shortened here; the file has them whole.