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.

32 changes behind one line · newest firstCSVJSONRSS

Since

One change, in full: Product added: visionos named as affected from apple. Products named as affected in 32 CVE records. Back to all 3 products in this change · Back to the ledger

Counted changes, newest first, one line per change to a CVE record or a GHSA advisory, 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 or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together.Vendor or package, 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-27Product addedCVE-2026-28979not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-39868not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-39872not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43663not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43676not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43699not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43700not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43701not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43703not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43704not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43705not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43706not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43707not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43708not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43709not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43712not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43713not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43715not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43718not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43720not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43721not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43724not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43725not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43726not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43727not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43731not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43732not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43734not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43735not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43740not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43742not named as affected at publication, now names visionosDays to revision 28
2026-07-27Product addedCVE-2026-43745not named as affected at publication, now names visionosDays to revision 28

Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. 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.

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 →