CVE publication and update activity
When the public catalogue published and last updated the records in scope. This describes the catalogue, not your remediation pace.
Public CVE records only. Nothing here is evidence that the vulnerability exists on your assets.
Data sources, exact rule, and what is unknown
Powered by: public.cves.published and public.cves.last_modified via fetchCves · public.cve_sync_state for freshness
Rule: Counts of catalogue records grouped by publication month and last-modified month, plus age bands measured from the publication date. All timestamps are rendered in your browser timezone.
- Publication activity is a property of the public catalogue, not of your environment.
- No patch recommendation is derived from publication or update activity.
Median days since publication
Published over 90 days ago
Not updated in 180+ days
Updated in the last 14 days
How this works — definitions, thresholds, and what to doShowHide
Counts are catalogue records grouped by publication month and by last-modified month. Age bands measure days since publication: 0–7, 8–30, 31–90 and over 90 days.
All dates come from the public catalogue and are rendered in your browser timezone.
Not shown here: your remediation speed, ticket ageing and SLA compliance are not assessed on this lens — publication activity is a property of the catalogue, not of your team. No patch recommendation is derived from it.