Skip to content

Every change, newest first

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

12 changes behind one line · newest firstCSVJSONRSS

SinceClear all
ChangedSourceRows

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

Counted changes from red hat, 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.KindRecord, 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 changedDays 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-07-072 commitsProduct addedCVE-2026-11610not named as affected at publication, now names red hat directory server 12.4 e4s for rhel 9 and 2 moreBranches and original-value intervals are stated on each row.Time to revision 0 days
2026-07-07same kind of change as the line aboveCVE-2026-11610same vendor as the line abovenot named as affected at publication, now names red hat directory server 12.4 e4s for rhel 9Time to revision 0 days
2026-07-07same kind of change as the line aboveCVE-2026-11610same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportTime to revision 0 days
2026-07-07same kind of change as the line aboveCVE-2026-11610same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update supportTime to revision 0 days
2026-07-072 commitsProduct addedCVE-2026-11774not named as affected at publication, now names red hat directory server 12.4 e4s for rhel 9 and 2 moreBranches and original-value intervals are stated on each row.Time to revision 26 days
2026-07-07same kind of change as the line aboveCVE-2026-11774same vendor as the line abovenot named as affected at publication, now names red hat directory server 12.4 e4s for rhel 9Time to revision 26 days
2026-07-07same kind of change as the line aboveCVE-2026-11774same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportTime to revision 26 days
2026-07-07same kind of change as the line aboveCVE-2026-11774same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update supportTime to revision 26 days
2026-07-072 commitsProduct addedCVE-2026-42009not named as affected at publication, now names red hat openshift container platform 4.20 and 1 moreBranches and original-value intervals are stated on each row.Time to revision 50 days
2026-07-07same kind of change as the line aboveCVE-2026-42009same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.20Time to revision 50 days
2026-07-07same kind of change as the line aboveCVE-2026-42009same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.21Time to revision 50 days
2026-07-073 commitsProduct addedCVE-2026-42010not named as affected at publication, now names red hat openshift container platform 4.20 and 2 moreBranches and original-value intervals are stated on each row.Time to revision 61 days
2026-07-07same kind of change as the line aboveCVE-2026-42010same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.20Time to revision 61 days
2026-07-07same kind of change as the line aboveCVE-2026-42010same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.21Time to revision 61 days
2026-07-07same kind of change as the line aboveCVE-2026-42010same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.22Time to revision 61 days
2026-07-07Product addedCVE-2026-9165not named as affected at publication, now names red hat advanced cluster security for kubernetes 4.11Time to revision 1 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.

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 →