Skip to content

Product added

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

11 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

Showing changes seen on 2026-07-23. Every day

Counted changes of "Product added" published by redhat, changed on 2026-07-23, 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.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 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.
Thu 23 Jul 2026· 11 record changes
2026-07-23CVE-2026-11332not named as affected at publication, now names migration toolkit for applications 8 and 4 moreDays to revision 49
2026-07-23CVE-2026-11332same vendor as the line abovenot named as affected at publication, now names migration toolkit for applications 8Days to revision 49
2026-07-23CVE-2026-11332same vendor as the line abovenot named as affected at publication, now names migration toolkit for virtualizationDays to revision 49
2026-07-23CVE-2026-11332same vendor as the line abovenot named as affected at publication, now names red hat ansible automation platform ansible core 2Days to revision 49
2026-07-23CVE-2026-11332same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4Days to revision 49
2026-07-23CVE-2026-11332same vendor as the line abovenot named as affected at publication, now names self-service automation portal 2Days to revision 49
2026-07-23CVE-2026-16615redhatnot named as affected at publication, now names librestDays to revision 1
2026-07-23not named as affected at publication, now names red hat update infrastructure 5Days to revision 23 to 422
2026-07-23CVE-2025-10911same vendor as the line abovesame change as the line aboveDays to revision 301
2026-07-23CVE-2025-5278same vendor as the line abovesame change as the line aboveDays to revision 422
2026-07-23CVE-2025-6170same vendor as the line abovesame change as the line aboveDays to revision 402
2026-07-23CVE-2026-48864same vendor as the line abovesame change as the line aboveDays to revision 58
2026-07-23CVE-2026-58016same vendor as the line abovesame change as the line aboveDays to revision 23

This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller. 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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

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 →