Product added

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

21 changes behind one line · newest firstCSV JSON RSS

One change, in full: Product added: safari named as affected from apple. Products named as affected in 21 CVE records. Back to the ledger

Counted changes of "Product added", 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-05-13	CVE-2026-28847	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28883	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28901	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28902	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28903	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28904	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28905	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28907	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28913	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28917	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28942	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28944	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28946	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28947	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28953	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28955	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28958	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28962	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-28971	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-43658	apple	not named as affected at publication, now names safari	Days to revision 2
2026-05-13	CVE-2026-43660	apple	not named as affected at publication, now names safari	Days to revision 2

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.

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 →