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.

11 changes behind one line · newest firstCSVJSONRSS

SinceClear all
ChangedSourceRows

One change, in full: Product added: 8 products named as affected from red hat. Products named as affected in 3 CVE records, across 8 products: 11 rows in all, one per record and product. Drawn here as 3 lines, one per product. Back to the ledger

Counted changes from red hat, 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-07-20Product addedCVE-2026-10649not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support and 1 moreDays to revision 34
2026-07-20same kind of change as the line aboveCVE-2026-10649same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportDays to revision 34
2026-07-20same kind of change as the line aboveCVE-2026-10649same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update supportDays to revision 34
2026-07-203 commitsProduct addedCVE-2026-11332not named as affected at publication, now names red hat ansible automation platform 2.6 for rhel 10 and 5 moreBranches and original-value intervals are stated on each row.Days to revision 45 to 46
2026-07-20same kind of change as the line aboveCVE-2026-11332same vendor as the line abovenot named as affected at publication, now names red hat ansible automation platform 2.6 for rhel 10Days to revision 46
2026-07-20same kind of change as the line aboveCVE-2026-11332same vendor as the line abovenot named as affected at publication, now names red hat ansible automation platform 2.6 for rhel 9Days to revision 46
2026-07-20same kind of change as the line aboveCVE-2026-11332same vendor as the line abovenot named as affected at publication, now names red hat ansible automation platform 2.5 for rhel 8Days to revision 46
2026-07-20same kind of change as the line aboveCVE-2026-11332same vendor as the line abovenot named as affected at publication, now names red hat ansible automation platform 2.5 for rhel 9Days to revision 46
2026-07-20same kind of change as the line aboveCVE-2026-11332same vendor as the line abovenot named as affected at publication, now names red hat ansible automation platform 2.7 for rhel 10Days to revision 45
2026-07-20same kind of change as the line aboveCVE-2026-11332same vendor as the line abovenot named as affected at publication, now names red hat ansible automation platform 2.7 for rhel 9Days to revision 45
2026-07-202 commitsProduct addedCVE-2026-12701not named as affected at publication, now names red hat ansible automation platform 2.6 for rhel 9 and 2 moreBranches and original-value intervals are stated on each row.Days to revision 0
2026-07-20same kind of change as the line aboveCVE-2026-12701same vendor as the line abovenot named as affected at publication, now names red hat ansible automation platform 2.6 for rhel 9Days to revision 0
2026-07-20same kind of change as the line aboveCVE-2026-12701same vendor as the line abovenot named as affected at publication, now names red hat ansible automation platform 2.5 for rhel 8Days to revision 0
2026-07-20same kind of change as the line aboveCVE-2026-12701same vendor as the line abovenot named as affected at publication, now names red hat ansible automation platform 2.5 for rhel 9Days to revision 0

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 →