Every change, newest first

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

72 changes · newest first · grouped by dayCSV JSON RSS

Counted changes from Microsoft, from the last 30 days, 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.	Kind	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.
Fri 4 Sep 2026· 1 change
2026-09-04	Ransomware use confirmed	CVE-2022-37969	MicrosoftWindows CISA KEV	stated at publication Unknown, now states Known	Duration unknown
Thu 3 Sep 2026· 1 change
2026-09-03	Product added	CVE-2026-58641	microsoft	not named as affected at publication, now names skiasharp	Time to revision 23 days
Wed 2 Sep 2026· 9 changes
2026-09-02	Fix version moved	CVE-2026-65675	microsoftmicrosoft visual studio code copilot chat extension	stated at publication 1.132.1, now states 1.135Release branch starts at 0.27.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02.	Time to revision 17 days
2026-09-02	Fix version moved	Show all 8 CVE records in this change: Fix version moved: 1.132.1 → 1.135 from microsoftHide the 8 CVE records in this change: Fix version moved: 1.132.1 → 1.135 from microsoft	microsoftvisual studio code	stated at publication 1.132.1, now states 1.135Release branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02.	Time to revision 17 days
2026-09-02	same kind of change as the line above	CVE-2026-58650	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02.	Time to revision 17 days
2026-09-02	same kind of change as the line above	CVE-2026-59113	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02.	Time to revision 17 days
2026-09-02	same kind of change as the line above	CVE-2026-47285	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02.	Time to revision 17 days
2026-09-02	same kind of change as the line above	CVE-2026-69320	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02.	Time to revision 17 days
2026-09-02	same kind of change as the line above	CVE-2026-69278	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02.	Time to revision 17 days
2026-09-02	same kind of change as the line above	CVE-2026-69306	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02.	Time to revision 17 days
2026-09-02	same kind of change as the line above	CVE-2026-70335	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02.	Time to revision 17 days
2026-09-02	same kind of change as the line above	CVE-2026-70336	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02.	Time to revision 17 days
Fri 28 Aug 2026· 1 change
2026-08-28	Product added	CVE-2026-59133	microsoft	not named as affected at publication, now names microsoft hpc pack 2019	Time to revision 17 days
Wed 26 Aug 2026· 1 change
2026-08-26	Added to CISA KEV	CVE-2019-1068	MicrosoftSQL Server CISA KEV	fix due 2026-08-29	Duration unknown
Fri 21 Aug 2026· 3 changes
2026-08-21	Added to CISA KEV	CVE-2026-69836	MicrosoftEntra ID CISA KEV	fix due 2026-08-24	Duration unknown
2026-08-21	Ransomware use confirmed	CVE-2021-43226	MicrosoftWindows CISA KEV	stated at publication Unknown, now states Known	Time to revision 319 days
2026-08-21	Ransomware use confirmed	CVE-2012-0158	MicrosoftMSCOMCTL.OCX CISA KEV	stated at publication Unknown, now states Known	Duration unknown
Tue 18 Aug 2026· 2 changes
2026-08-18	Added to CISA KEV	CVE-2026-33824	MicrosoftInternet Key Exchange (IKE) Service Extensions CISA KEV	fix due 2026-08-21	Duration unknown
2026-08-18	Added to CISA KEV	CVE-2026-55040	MicrosoftSharePoint CISA KEV	fix due 2026-08-21	Duration unknown
Sun 16 Aug 2026· 1 change
2026-08-16	Product added	CVE-2026-59124	microsoft	not named as affected at publication, now names microsoft hpc pack 2019	Time to revision 5 days
Fri 14 Aug 2026· 25 changes
2026-08-14	Ransomware use confirmed	CVE-2025-60710	MicrosoftWindows CISA KEV	stated at publication Unknown, now states Known	Time to revision 123 days
2026-08-14	Ransomware use confirmed	CVE-2020-0618	MicrosoftSQL Server CISA KEV	stated at publication Unknown, now states Known	Duration unknown
2026-08-14	Ransomware use confirmed	Show all 2 CVE records in this change: Ransomware use confirmed: Unknown → Known from MicrosoftHide the 2 CVE records in this change: Ransomware use confirmed: Unknown → Known from Microsoft	MicrosoftInternet Explorer	stated at publication Unknown, now states Known	Duration unknown
2026-08-14	same kind of change as the line above	CVE-2016-0189	same vendor as the line above	same change as the line above	Duration unknown
2026-08-14	same kind of change as the line above	CVE-2020-0968	same vendor as the line above	same change as the line above	Duration unknown
2026-08-14	Ransomware use confirmed	Show all 2 CVE records in this change: Ransomware use confirmed: Unknown → Known from MicrosoftHide the 2 CVE records in this change: Ransomware use confirmed: Unknown → Known from Microsoft	MicrosoftWin32k	stated at publication Unknown, now states Known	Duration unknown
2026-08-14	same kind of change as the line above	CVE-2022-21882	same vendor as the line above	same change as the line above	Duration unknown
2026-08-14	same kind of change as the line above	CVE-2019-0803	same vendor as the line above	same change as the line above	Duration unknown
2026-08-14	Ransomware use confirmed	CVE-2018-0802	MicrosoftOffice CISA KEV	stated at publication Unknown, now states Known	Duration unknown
2026-08-14	Fix version moved	CVE-2026-32202Show all 3 products in this change: Fix version moved: 10.0.14393.9060 → 10.0.14393.9339 in CVE-2026-32202Hide the 3 products in this change: Fix version moved: 10.0.14393.9060 → 10.0.14393.9339 in CVE-2026-32202	microsoft3 products	stated at publication 10.0.14393.9060, now states 10.0.14393.9339Release branch starts at 10.0.14393.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.14393.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.14393.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.14393.0.	Time to revision 122 days
2026-08-14	Fix version moved	CVE-2026-32202Show all 3 products in this change: Fix version moved: 10.0.17763.8644 → 10.0.17763.9020 in CVE-2026-32202Hide the 3 products in this change: Fix version moved: 10.0.17763.8644 → 10.0.17763.9020 in CVE-2026-32202	microsoft3 products	stated at publication 10.0.17763.8644, now states 10.0.17763.9020Release branch starts at 10.0.17763.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.17763.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.17763.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.17763.0.	Time to revision 122 days
2026-08-14	Fix version moved	CVE-2026-32202	microsoftwindows 10 version 21h2	stated at publication 10.0.19044.7184, now states 10.0.19044.7548Release branch starts at 10.0.19044.0.	Time to revision 122 days
2026-08-14	Fix version moved	CVE-2026-32202	microsoftwindows 10 version 22h2	stated at publication 10.0.19045.7184, now states 10.0.19045.7548Release branch starts at 10.0.19045.0.	Time to revision 122 days
2026-08-14	Fix version moved	CVE-2026-32202	microsoftwindows 11 version 23h2	stated at publication 10.0.22631.6936, now states 10.0.22631.7376Release branch starts at 10.0.22631.0.	Time to revision 122 days
2026-08-14	Fix version moved	CVE-2026-32202	microsoftwindows 11 version 25h2	stated at publication 10.0.26200.8246, now states 10.0.26200.8875Release branch starts at 10.0.26200.0.	Time to revision 122 days
2026-08-14	Fix version moved	CVE-2026-32202	microsoftwindows 11 version 26h1	stated at publication 10.0.28000.1836, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.	Time to revision 122 days
2026-08-14	Fix version moved	CVE-2026-32202Show all 2 products in this change: Fix version moved: 6.2.9200.26026 → 6.2.9200.26226 in CVE-2026-32202Hide the 2 products in this change: Fix version moved: 6.2.9200.26026 → 6.2.9200.26226 in CVE-2026-32202	microsoft2 products	stated at publication 6.2.9200.26026, now states 6.2.9200.26226Release branch starts at 6.2.9200.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 6.2.9200.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 6.2.9200.0.	Time to revision 122 days
2026-08-14	Fix version moved	CVE-2026-32202Show all 2 products in this change: Fix version moved: 6.3.9600.23132 → 6.3.9600.23291 in CVE-2026-32202Hide the 2 products in this change: Fix version moved: 6.3.9600.23132 → 6.3.9600.23291 in CVE-2026-32202	microsoft2 products	stated at publication 6.3.9600.23132, now states 6.3.9600.23291Release branch starts at 6.3.9600.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 6.3.9600.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 6.3.9600.0.	Time to revision 122 days
2026-08-14	Fix version moved	CVE-2026-32202	microsoftwindows server 2022	stated at publication 10.0.20348.5020, now states 10.0.20348.5386Release branch starts at 10.0.20348.0.	Time to revision 122 days
2026-08-14	Fix version moved	CVE-2026-32202Show all 2 products in this change: Fix version moved: 10.0.26100.32690 → 10.0.26100.33158 in CVE-2026-32202Hide the 2 products in this change: Fix version moved: 10.0.26100.32690 → 10.0.26100.33158 in CVE-2026-32202	microsoft2 products	stated at publication 10.0.26100.32690, now states 10.0.26100.33158Release branch starts at 10.0.26100.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 122 days
2026-08-14	same kind of change as the line above	CVE-2026-32202	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 122 days
Thu 13 Aug 2026· 25 changes
2026-08-13	Product added	Show all 25 CVE records in this change: Product added: office online server named as affected from microsoftHide the 25 CVE records in this change: Product added: office online server named as affected from microsoft	microsoft	not named as affected at publication, now names office online server	Time to revision 2 days
2026-08-13	same kind of change as the line above	CVE-2026-65807	same vendor as the line above	same change as the line above	Time to revision 2 days
2026-08-13	same kind of change as the line above	CVE-2026-68793	same vendor as the line above	same change as the line above	Time to revision 2 days
2026-08-13	same kind of change as the line above	CVE-2026-68794	same vendor as the line above	same change as the line above	Time to revision 2 days
2026-08-13	same kind of change as the line above	CVE-2026-68795	same vendor as the line above	same change as the line above	Time to revision 2 days
2026-08-13	same kind of change as the line above	CVE-2026-68796	same vendor as the line above	same change as the line above	Time to revision 2 days
2026-08-13	same kind of change as the line above	CVE-2026-68797	same vendor as the line above	same change as the line above	Time to revision 2 days
2026-08-13	same kind of change as the line above	CVE-2026-68799	same vendor as the line above	same change as the line above	Time to revision 2 days
2026-08-13	same kind of change as the line above	CVE-2026-68800	same vendor as the line above	same change as the line above	Time to revision 2 days
17 more rows in this change are not listed here. Open all 25 rows →
Tue 11 Aug 2026· 2 changes
2026-08-11	Added to CISA KEV	CVE-2026-68820	MicrosoftWindows Ancillary Function Driver for WinSock CISA KEV	fix due 2026-08-25	Duration unknown
2026-08-11	Product added	CVE-2026-59118	microsoft	not named as affected at publication, now names copilot cowork	Time to revision 5 days
Mon 10 Aug 2026· 1 change
2026-08-10	Ransomware use confirmed	CVE-2026-45659	MicrosoftSharePoint Server CISA KEV	stated at publication Unknown, now states Known	Time to revision 40 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

Every kind of change

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub 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 →