Every change, newest first

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

17 changes behind one line · newest firstCSV JSON RSS

SinceKindVendorSortClear all

Showing changes seen on 2026-03-26. Every day

One change, in full: Product added: 4 products named as affected from red hat. The same change in 5 CVE records, across 4 products: 17 rows in all. Drawn here as 4 lines, one per product. Back to the ledger

Counted changes changed on 2026-03-26, 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-03-26	Product added	Show all 4 CVE records in this change: Product added: red hat satellite 6.18 for rhel 9 named as affected from red hatHide the 4 CVE records in this change: Product added: red hat satellite 6.18 for rhel 9 named as affected from red hat	red hat	not named as affected at publication, now names red hat satellite 6.18 for rhel 9	Time to revision 0 to 53 days
2026-03-26	same kind of change as the line above	CVE-2026-0980	same vendor as the line above	same change as the line above	Time to revision 28 days
2026-03-26	same kind of change as the line above	CVE-2026-1531	same vendor as the line above	same change as the line above	Time to revision 53 days
2026-03-26	same kind of change as the line above	CVE-2026-1961	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-03-26	same kind of change as the line above	CVE-2026-4324	same vendor as the line above	same change as the line above	Time to revision 9 days
2026-03-26	Product added	Show all 4 CVE records in this change: Product added: red hat satellite 6.16 for rhel 8 named as affected from red hatHide the 4 CVE records in this change: Product added: red hat satellite 6.16 for rhel 8 named as affected from red hat	red hat	not named as affected at publication, now names red hat satellite 6.16 for rhel 8	Time to revision 0 to 53 days
2026-03-26	same kind of change as the line above	CVE-2026-0980	same vendor as the line above	same change as the line above	Time to revision 28 days
2026-03-26	same kind of change as the line above	CVE-2026-1530	same vendor as the line above	same change as the line above	Time to revision 53 days
2026-03-26	same kind of change as the line above	CVE-2026-1531	same vendor as the line above	same change as the line above	Time to revision 53 days
2026-03-26	same kind of change as the line above	CVE-2026-1961	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-03-26	Product added	Show all 4 CVE records in this change: Product added: red hat satellite 6.16 for rhel 9 named as affected from red hatHide the 4 CVE records in this change: Product added: red hat satellite 6.16 for rhel 9 named as affected from red hat	red hat	not named as affected at publication, now names red hat satellite 6.16 for rhel 9	Time to revision 0 to 53 days
2026-03-26	same kind of change as the line above	CVE-2026-0980	same vendor as the line above	same change as the line above	Time to revision 28 days
2026-03-26	same kind of change as the line above	CVE-2026-1530	same vendor as the line above	same change as the line above	Time to revision 53 days
2026-03-26	same kind of change as the line above	CVE-2026-1531	same vendor as the line above	same change as the line above	Time to revision 53 days
2026-03-26	same kind of change as the line above	CVE-2026-1961	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-03-26	Product added	Show all 5 CVE records in this change: Product added: red hat satellite 6.17 for rhel 9 named as affected from red hatHide the 5 CVE records in this change: Product added: red hat satellite 6.17 for rhel 9 named as affected from red hat	red hat	not named as affected at publication, now names red hat satellite 6.17 for rhel 9	Time to revision 0 to 53 days
2026-03-26	same kind of change as the line above	CVE-2026-0980	same vendor as the line above	same change as the line above	Time to revision 28 days
2026-03-26	same kind of change as the line above	CVE-2026-1530	same vendor as the line above	same change as the line above	Time to revision 53 days
2026-03-26	same kind of change as the line above	CVE-2026-1531	same vendor as the line above	same change as the line above	Time to revision 53 days
2026-03-26	same kind of change as the line above	CVE-2026-1961	same vendor as the line above	same change as the line above	Time to revision 0 days
2026-03-26	same kind of change as the line above	CVE-2026-4324	same vendor as the line above	same change as the line above	Time to revision 9 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

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 →