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.

12 changes behind one line · newest firstCSVJSONRSS

SinceClear all

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

One change, in full: Product added: microsoft .net framework 4.8.1 named as affected from microsoft. The same change in 12 CVE records. Back to the ledger

Counted changes from microsoft, changed on 2026-07-22, 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-07-22Product addedCVE-2026-47304not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 days
2026-07-22Product addedCVE-2026-50304not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 days
2026-07-22Product addedCVE-2026-50324not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 days
2026-07-22Product addedCVE-2026-50355not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 days
2026-07-22Product addedCVE-2026-50368not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 days
2026-07-22Product addedCVE-2026-50411not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 days
2026-07-22Product addedCVE-2026-50525not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 days
2026-07-22Product addedCVE-2026-50647not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 days
2026-07-22Product addedCVE-2026-50649not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 days
2026-07-22Product addedCVE-2026-50652not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 days
2026-07-22Product addedCVE-2026-50653not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 days
2026-07-22Product addedCVE-2026-50659not named as affected at publication, now names microsoft .net framework 4.8.1Time to revision 8 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 →