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.

21 changes behind one line · newest firstCSVJSONRSS

SinceClear all
ChangedSourceRows

Showing changes seen on 2026-05-13. Every day

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

Counted changes changed on 2026-05-13, 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-05-13Product addedCVE-2026-28847not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28883not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28901not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28902not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28903not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28904not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28905not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28907not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28913not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28917not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28942not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28944not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28946not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28947not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28953not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28955not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28958not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28962not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-28971not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-43658not named as affected at publication, now names safariTime to revision 2 days
2026-05-13Product addedCVE-2026-43660not named as affected at publication, now names safariTime to revision 2 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.

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 →