Every change, newest first

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

21 changes behind one line · newest firstCSV JSON RSS

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

Counted changes from the last 30 days, newest first, one line per change to a CVE record or a GHSA advisory, 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 or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together.	Vendor or package, 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-08-18	Product added	Show all 2 CVE records in this change: Product added: red hat build of keycloak 26.6 named as affected from red hatHide the 2 CVE records in this change: Product added: red hat build of keycloak 26.6 named as affected from red hat	red hat	not named as affected at publication, now names red hat build of keycloak 26.6	Time to revision 25 to 46 days
2026-08-18	same kind of change as the line above	CVE-2026-14613	same vendor as the line above	same change as the line above	Time to revision 46 days
2026-08-18	same kind of change as the line above	CVE-2026-17048	same vendor as the line above	same change as the line above	Time to revision 25 days
2026-08-18	Product added	CVE-2026-75924	red hat	not named as affected at publication, now names multicluster engine for kubernetes	Time to revision 0 days
2026-08-182 commits	Product added	Show all 3 CVE records in this change: Product added: red hat directory server 12.4 e4s for rhel 9 named as affected from red hatHide the 3 CVE records in this change: Product added: red hat directory server 12.4 e4s for rhel 9 named as affected from red hat	red hat	not named as affected at publication, now names red hat directory server 12.4 e4s for rhel 9Branches and original-value intervals are stated on each row.	Time to revision 18 to 70 days
2026-08-18	same kind of change as the line above	CVE-2026-11770	same vendor as the line above	same change as the line above	Time to revision 18 days
2026-08-18	same kind of change as the line above	CVE-2026-11788	same vendor as the line above	same change as the line above	Time to revision 70 days
2026-08-18	same kind of change as the line above	CVE-2026-15722	same vendor as the line above	same change as the line above	Time to revision 18 days
2026-08-183 commits	Product added	Show all 5 CVE records in this change: Product added: red hat openshift container platform 4.22 named as affected from red hatHide the 5 CVE records in this change: Product added: red hat openshift container platform 4.22 named as affected from red hat	red hat	not named as affected at publication, now names red hat openshift container platform 4.22Branches and original-value intervals are stated on each row.	Time to revision 21 to 83 days
2026-08-18	same kind of change as the line above	CVE-2026-14164	same vendor as the line above	same change as the line above	Time to revision 49 days
2026-08-18	same kind of change as the line above	CVE-2026-14476	same vendor as the line above	same change as the line above	Time to revision 42 days
2026-08-18	same kind of change as the line above	CVE-2026-14474	same vendor as the line above	same change as the line above	Time to revision 42 days
2026-08-18	same kind of change as the line above	CVE-2026-16313	same vendor as the line above	same change as the line above	Time to revision 21 days
2026-08-18	same kind of change as the line above	CVE-2026-1933	same vendor as the line above	same change as the line above	Time to revision 83 days
2026-08-182 commits	Product added	Show all 4 CVE records in this change: Product added: red hat openshift container platform 4.20 named as affected from red hatHide the 4 CVE records in this change: Product added: red hat openshift container platform 4.20 named as affected from red hat	red hat	not named as affected at publication, now names red hat openshift container platform 4.20Branches and original-value intervals are stated on each row.	Time to revision 42 to 448 days
2026-08-18	same kind of change as the line above	CVE-2025-5222	same vendor as the line above	same change as the line above	Time to revision 448 days
2026-08-18	same kind of change as the line above	CVE-2026-14476	same vendor as the line above	same change as the line above	Time to revision 42 days
2026-08-18	same kind of change as the line above	CVE-2026-14474	same vendor as the line above	same change as the line above	Time to revision 42 days
2026-08-18	same kind of change as the line above	CVE-2026-1933	same vendor as the line above	same change as the line above	Time to revision 83 days
2026-08-18	Product added	Show all 3 CVE records in this change: Product added: red hat openshift container platform 4.21 named as affected from red hatHide the 3 CVE records in this change: Product added: red hat openshift container platform 4.21 named as affected from red hat	red hat	not named as affected at publication, now names red hat openshift container platform 4.21	Time to revision 42 to 83 days
2026-08-18	same kind of change as the line above	CVE-2026-14474	same vendor as the line above	same change as the line above	Time to revision 42 days
2026-08-18	same kind of change as the line above	CVE-2026-14476	same vendor as the line above	same change as the line above	Time to revision 42 days
2026-08-18	same kind of change as the line above	CVE-2026-1933	same vendor as the line above	same change as the line above	Time to revision 83 days
2026-08-182 commits	Product added	Show all 3 CVE records in this change: Product added: red hat directory server 12.2 e4s for rhel 9 named as affected from red hatHide the 3 CVE records in this change: Product added: red hat directory server 12.2 e4s for rhel 9 named as affected from red hat	red hat	not named as affected at publication, now names red hat directory server 12.2 e4s for rhel 9Branches and original-value intervals are stated on each row.	Time to revision 18 to 70 days
2026-08-18	same kind of change as the line above	CVE-2026-11770	same vendor as the line above	same change as the line above	Time to revision 18 days
2026-08-18	same kind of change as the line above	CVE-2026-11788	same vendor as the line above	same change as the line above	Time to revision 70 days
2026-08-18	same kind of change as the line above	CVE-2026-15722	same vendor as the line above	same change as the line above	Time to revision 18 days

Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. 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 →