Summary
- The National Institute of Standards and Technology grades each vulnerability record in its National Vulnerability Database with one of seven status words, and across the status page, the dashboard and the API documentation those seven states carry thirteen different printed names; the dashboard's seven counts sum exactly to its printed total of 430,439.
- Nothing on the ten pages read for this piece on 22 November 2026 dates the moment a record entered its state, and the API documentation itself says the record's modification timestamp does not move when the status changes to Undergoing Analysis — so the queue can be counted and not timed.
The National Vulnerability Database does not merely store vulnerability records. It grades them, and it prints the grade where anyone can read it. On 22 November 2026 the vulnerability status page carried a table with three columns, headed NVD Status, NVD API Status and Description, and seven rows. Here are the seven defining sentences as that page prints them, in order.
Received: "The CVE has recently been published to the CVE List and is now included within the NVD dataset." Awaiting Enrichment: "The CVE has been marked for NVD enrichment efforts." Undergoing Enrichment: "The CVE is currently being enriched by the NVD Enrichment team. The enrichment process results in the association of reference link tags, CVSS, CWE, and CPE applicability statement data." Enriched: "NVD's CVE enrichment process is complete.
CVEs in this status do not show a banner on the vulnerability detail page." Modified After Enrichment: "The CVE record has been updated after NVD enrichment efforts were completed. Enrichment data supplied by the NVD may require amendment due to these changes. Although not routinely reviewed, requests may be made for review." Not Scheduled: "The CVE is not currently scheduled for NVD enrichment efforts. The CVE may be out of NVD's declared scope of coverage or has not been prioritized due to resource or other concerns.
Requests may be made to schedule for enrichment." Rejected: "The CVE has been marked Rejected in the CVE List. Rejection of a CVE is determined by the CVE Program and not the NVD."
Two of those seven sentences name a party. Undergoing Enrichment names "the NVD Enrichment team". Rejected names "the CVE Program and not the NVD". The other five describe a state of the record and never say who moved it there. Not one of the seven carries a target interval, a service level, a dwell time or a queue depth; the only expression of time across the whole table is the word "recently". The table also has no column, field or footnote giving the date on which a record entered any of these states.
The only dates on the page sit in its footer, and they describe the page: Created Sep 20, 2022, Updated Apr 14, 2026.
The machine-readable side is plainer about what is guaranteed and vaguer about what it means. The CVE API 2.0 documentation states that the required record object "always contains the CVE-ID, sourceIdentifier an identifier for the source of the CVE, published the date and time that the CVE was published to the NVD, lastModified the date and time that the CVE was last modified, and vulnStatus the CVE's status in the NVD." That is the whole published description of the status field: five words, no list of values, no definition of any of them. The seven API names come instead from the second column of the status page, which prints Awaiting Analysis, Undergoing Analysis, Analyzed, Modified and Deferred beside the human labels.
Then comes the sentence that decides the argument. Among the actions that do not change lastModified, the documentation lists a specific one: the NVD changing the status of a newly published CVE record to "Undergoing Analysis". A record can therefore enter the analysis queue without its modification timestamp moving at all. Anyone using that timestamp as a clock is measuring the wrong thing.
One record shows the schema doing its job and doing no more. The API response for CVE-2021-44228 returned a single result carrying published 2021-12-10T10:15:09.143, lastModified 2026-08-11T19:33:44.513, vulnStatus Analyzed, and a source identifier naming the originating project. That is the full set of fields the documentation promises, and none of them is the date the record became Analyzed. Its detail page is consistent with the vocabulary: it prints Published Dec 10, 2021, Last Modified Aug 11, 2026 and the source, and no status banner, exactly as the Enriched definition promises for records whose enrichment is complete.
The two records that are not complete tell the sharper story. CVE-2016-0070 carries a banner reading "Not Scheduled" above one sentence: "This CVE record is not being prioritized for NVD enrichment efforts due to resource or other concerns." Its Quick Info block prints NVD Published Date 10/13/2016, NVD Last Modified 04/12/2025 and Source Microsoft Corporation. CVE-2026-20053 carries a banner reading "Awaiting Analysis" above "This CVE record has been marked for NVD enrichment efforts.", and prints NVD Published Date 03/04/2026, NVD Last Modified 03/05/2026 and Source Cisco Systems, Inc. Neither banner dates itself. The second record was published on 4 March 2026 and was still awaiting analysis on 22 November 2026 — 263 days — while the only movement its page records is a modification dated one day after publication. That interval is a fact about how old the record is. It is not a waiting time, because no reviewed surface prints the moment the waiting began. And the Not Scheduled definition offers two candidate reasons for a record's placement — outside declared scope, or not prioritised for resource or other concerns — without printing which one applied to this record.
The counts are the strongest part of the instrument. The NVD Dashboard prints Total 430,439, with Received 7,367, Analyzed 80,830, Awaiting Analysis 11,879, Undergoing Analysis 988, Modified After Analysis 245,796, Deferred 64,383 and Rejected 19,196. Add those seven figures and you get 430,439 exactly. The arithmetic is perfect, and it should be said plainly: an audience braced for a discrepancy will not find one here. What the perfect sum proves is that these are counts of records sitting in states at one instant, not a flow of work. Three of those states mean analysis has not finished: Received, Awaiting Analysis and Undergoing Analysis hold 20,234 records between them, 4.7 per cent of the printed total. The dashboard labels the same seven states a third way, printing Modified After Analysis where the status page prints Modified After Enrichment and Modified, and it prints no date and no time at which these counts were taken.
All of this leaves one question the instrument can answer and one it cannot. The clock exists, and it is narrow: NVD's process page prints a single timing target — "Within one business day of addition to the KEV Catalog" — for records listed in CISA's Known Exploited Vulnerabilities Catalog, alongside a general note that records are typically in NVD within an hour of CVE List publication and that enrichment time "can vary depending on the CVE, the information available, and the quantity of CVEs published within a given timeframe". NIST's 15 April 2026 operations announcement states the same goal for the same population with a different anchor — "within one business day of receipt" — and adds the risk-based priority order: Known Exploited Vulnerabilities first, then software used within the federal government, then critical software under Executive Order 14028, with everything else listed but categorised as lowest priority and not scheduled for immediate enrichment. Across the ten documents read on 22 November 2026, the number of published intervals covering a record outside the Known Exploited Vulnerabilities category is zero.
What the instrument cannot answer is whether a record is early or late in its state. The Not Scheduled definition invites the reader to act — "Requests may be made to schedule for enrichment" — and the Modified After Enrichment definition does the same for review, but neither prints a route, a clock or a record that an answer was given. NIST's 2 April 2025 program page shows the invitation is not decorative: it announced that pre-2018 records awaiting enrichment would be marked Deferred, promised that such records would display a banner explaining the status, explained the placement by the record's age, and committed to prioritising anything added to the Known Exploited Vulnerabilities Catalog regardless of status. The banner arrived. The route did not.
This is where the piece departs from earlier coverage. The publisher's directory record carries eleven earlier articles, among them a briefing on the FIPS 140-3 validation register, a run of briefings on NIST draft guidance, and a piece on the institute's time servers. None of them reads a vulnerability record's status field as an instrument: none asks what the state word obliges, who moves a record into it, on what clock, or whether the record dates the moment the word was applied.
Two consequences follow, and they are practical. A patch team that treats "Awaiting Analysis" as a queue position has no way to distinguish a record that arrived yesterday from one that has sat for nine months, and CVE-2026-20053 is the proof that nine months happens. A reader who wants to argue that a record was neglected cannot make that argument from the public record either, because a state with no reason and no date is not evidence of delay; it is evidence of an undated state.
The fix is a field, not an accusation: a status-set timestamp beside the state, a published route for the request the definitions invite, and an as-of time on the counts that reconcile so well without one. Until a page prints when the word was applied, the database's most precise numbers describe a queue whose length anyone can measure and whose waiting anyone must take on faith.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






