Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

10 changes behind one line · newest firstCSV JSON RSS

PublisherPublishedChangedSourceRows

One change, in full: Product added: red hat discovery 2 named as affected from red hat. The same change in 10 CVE records. Back to the ledger

Counted changes published by redhat, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.	Kind	Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on.	Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.	What changed	Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
2026-09-01	Product added	CVE-2026-15588	red hat	not named as affected at publication, now names red hat discovery 2	Time to revision 43 days
2026-09-01	Product added	CVE-2026-18477	red hat	not named as affected at publication, now names red hat discovery 2	Time to revision 29 days
2026-09-01	Product added	CVE-2026-18508	red hat	not named as affected at publication, now names red hat discovery 2	Time to revision 29 days
2026-09-01	Product added	CVE-2026-58010	red hat	not named as affected at publication, now names red hat discovery 2	Time to revision 63 days
2026-09-01	Product added	CVE-2026-58011	red hat	not named as affected at publication, now names red hat discovery 2	Time to revision 63 days
2026-09-01	Product added	CVE-2026-58012	red hat	not named as affected at publication, now names red hat discovery 2	Time to revision 63 days
2026-09-01	Product added	CVE-2026-58013	red hat	not named as affected at publication, now names red hat discovery 2	Time to revision 63 days
2026-09-01	Product added	CVE-2026-58014	red hat	not named as affected at publication, now names red hat discovery 2	Time to revision 63 days
2026-09-01	Product added	CVE-2026-58015	red hat	not named as affected at publication, now names red hat discovery 2	Time to revision 63 days
2026-09-01	Product added	CVE-2026-5704	red hat	not named as affected at publication, now names red hat discovery 2	Time to revision 148 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.

Every kind of change

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub advisory

What this page cannot see

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.

The units, the refusals, the cut-offs and every source, in full →

Paste your closed CVE tickets and see which of these changes hit them →