Coverage

The activity list and keyword search cover retained events, newest first. Defaults are a seven-day initial backfill, 30 days of activity, and score updates for 90 days after a CVE’s original publication. This is a recent feed, not an all-time archive.

Search a complete CVE ID to look up an older official record directly. These results are labelled RECORD and do not create new feed activity. Keyword searches match the retained IDs, products, source titles or excerpts, and compact affected-version statements.

NEW uses the original publication date. UPDATE represents a meaningful change observed between checks, including score revisions and corrections. The same CVE can therefore appear more than once. RSS contains the most recent 2,000 events, each with a distinct, durable identity.

The timestamp shows the last completed refresh, with newly added visible CVEs in brackets. An unchanged check shows [0 new]; score updates are not counted as new CVEs. The cloud refresh target is 30 minutes. An open page checks for new data every minute; upstream and RSS reader polling can add delay.

Scores

Prefer the CNA, then the CVE Program ADP, then other providers by organization ID. For that provider prefer CVSS 4.0, 3.1, 3.0, then 2.0. Prefer an explicitly general assessment; otherwise retain the selected version’s scenarios together. Every entry gives the version and provider. Unscored does not mean safe.

Severity sorting groups source severity categories from Critical down, then groups CVSS versions and orders scores within each version. Unscored, multiple-scenario, and rejected records follow. Scores from different versions are not directly equivalent. A scenario is never silently chosen for having the largest score. Event scores reflect the source at the event time; RECORD lookups show the current source.