Product added

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

17 changes behind one line · newest firstCSV JSON RSS

SinceKindVendorSortClear all

PublisherPublishedChangedSourceRows

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

Counted changes of "Product added" 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.	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 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-06	Show all 4 CVE records in this change: Product added: red hat enterprise linux ai 3.3 for rhel 9 named as affected from red hatHide the 4 CVE records in this change: Product added: red hat enterprise linux ai 3.3 for rhel 9 named as affected from red hat	red hat	not named as affected at publication, now names red hat enterprise linux ai 3.3 for rhel 9	Time to revision 48 days
2026-08-06	CVE-2026-56208	same vendor as the line above	same change as the line above	Time to revision 48 days
2026-08-06	CVE-2026-56209	same vendor as the line above	same change as the line above	Time to revision 48 days
2026-08-06	CVE-2026-56210	same vendor as the line above	same change as the line above	Time to revision 48 days
2026-08-06	CVE-2026-56211	same vendor as the line above	same change as the line above	Time to revision 48 days
2026-08-06	Show all 4 CVE records in this change: Product added: red hat enterprise linux ai 3.4 for rhel 9 named as affected from red hatHide the 4 CVE records in this change: Product added: red hat enterprise linux ai 3.4 for rhel 9 named as affected from red hat	red hat	not named as affected at publication, now names red hat enterprise linux ai 3.4 for rhel 9	Time to revision 48 days
2026-08-06	CVE-2026-56208	same vendor as the line above	same change as the line above	Time to revision 48 days
2026-08-06	CVE-2026-56209	same vendor as the line above	same change as the line above	Time to revision 48 days
2026-08-06	CVE-2026-56210	same vendor as the line above	same change as the line above	Time to revision 48 days
2026-08-06	CVE-2026-56211	same vendor as the line above	same change as the line above	Time to revision 48 days
2026-08-06	CVE-2026-58016Show all 2 products in this change: Product added: 2 products named as affected in CVE-2026-58016Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2026-58016	red hat	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support and 1 more	Time to revision 37 days
2026-08-06	CVE-2026-58016	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Time to revision 37 days
2026-08-06	CVE-2026-58016	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support	Time to revision 37 days
2026-08-06	CVE-2026-13201	red hat	not named as affected at publication, now names red hat container native virtualization 4.22	Time to revision 43 days
2026-08-06	CVE-2025-57848Show all 5 products in this change: Product added: 5 products named as affected in CVE-2025-57848Hide the 5 products in this change: Product added: 5 products named as affected in CVE-2025-57848	red hat	not named as affected at publication, now names rhel-8-cnv-4.12 and 4 more	Time to revision 287 days
2026-08-06	CVE-2025-57848	same vendor as the line above	not named as affected at publication, now names rhel-8-cnv-4.12	Time to revision 287 days
2026-08-06	CVE-2025-57848	same vendor as the line above	not named as affected at publication, now names rhel-9-cnv-4.14	Time to revision 287 days
2026-08-06	CVE-2025-57848	same vendor as the line above	not named as affected at publication, now names rhel-9-cnv-4.17	Time to revision 287 days
2026-08-06	CVE-2025-57848	same vendor as the line above	not named as affected at publication, now names rhel-9-cnv-4.18	Time to revision 287 days
2026-08-06	CVE-2025-57848	same vendor as the line above	not named as affected at publication, now names rhel-9-cnv-4.19	Time to revision 287 days
2026-08-06	CVE-2026-16242	red hat	not named as affected at publication, now names red hat openshift container platform 4.17	Time to revision 17 days

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. 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 →