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.

24 changes behind one line · newest firstCSVJSONRSS

SinceClear the filter
ChangedSourceRows

One change, in full: Product added: 6 products named as affected from red hat. Products named as affected in 14 CVE records, across 6 products: 24 rows in all, one per record and product. Drawn here as 4 lines, one per product. 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.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-06-292 commitsProduct addedCVE-2025-10911not named as affected at publication, now names red hat discovery 2 and 1 moreBranches and original-value intervals are stated on each row.Days to revision 277
2026-06-29same kind of change as the line aboveCVE-2025-10911same vendor as the line abovenot named as affected at publication, now names red hat discovery 2Days to revision 277
2026-06-29same kind of change as the line aboveCVE-2025-10911same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.6 extended update support long-life add-onDays to revision 277
2026-06-293 commitsProduct addednot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportBranches and original-value intervals are stated on each row.Days to revision 42 to 140
2026-06-29same kind of change as the line aboveCVE-2025-14831same vendor as the line abovesame change as the line aboveDays to revision 140
2026-06-29same kind of change as the line aboveCVE-2026-33846same vendor as the line abovesame change as the line aboveDays to revision 57
2026-06-29same kind of change as the line aboveCVE-2026-42009same vendor as the line abovesame change as the line aboveDays to revision 42
2026-06-29same kind of change as the line aboveCVE-2026-42010same vendor as the line abovesame change as the line aboveDays to revision 53
2026-06-29same kind of change as the line aboveCVE-2026-33845same vendor as the line abovesame change as the line aboveDays to revision 60
2026-06-292 commitsProduct addednot named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update supportBranches and original-value intervals are stated on each row.Days to revision 13 to 504
2026-06-29same kind of change as the line aboveCVE-2024-12133same vendor as the line abovesame change as the line aboveDays to revision 504
2026-06-29same kind of change as the line aboveCVE-2025-14831same vendor as the line abovesame change as the line aboveDays to revision 140
2026-06-29same kind of change as the line aboveCVE-2026-33845same vendor as the line abovesame change as the line aboveDays to revision 60
2026-06-29same kind of change as the line aboveCVE-2026-33846same vendor as the line abovesame change as the line aboveDays to revision 56
2026-06-29same kind of change as the line aboveCVE-2026-3833same vendor as the line abovesame change as the line aboveDays to revision 60
2026-06-29same kind of change as the line aboveCVE-2026-42009same vendor as the line abovesame change as the line aboveDays to revision 42
2026-06-29same kind of change as the line aboveCVE-2026-42010same vendor as the line abovesame change as the line aboveDays to revision 53
2026-06-29same kind of change as the line aboveCVE-2026-42011same vendor as the line abovesame change as the line aboveDays to revision 53
6 more rows in this change are not listed here. Open all 14 rows
2026-06-29Product addedCVE-2024-12133not named as affected at publication, now names red hat enterprise linux 8.6 extended update support long-life add-on and 2 moreDays to revision 504
2026-06-29same kind of change as the line aboveCVE-2024-12133same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.6 extended update support long-life add-onDays to revision 504
2026-06-29same kind of change as the line aboveCVE-2024-12133same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.8 telecommunications update serviceDays to revision 504
2026-06-29same kind of change as the line aboveCVE-2024-12133same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.8 update services for sap solutionsDays to revision 504

Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

Data sources and quality

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 →

Check my CVEs against these changes →