Every change, newest first

Compare earlier and later source statements, with the dates and evidence behind each measured change.

674 changes · newest first · grouped by dayCSV JSON RSS

PublisherPublishedChangedSourceRows

Counted changes published by microsoft, 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.
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
Thu 27 Aug 2026· 1 change
2026-08-27	CVSS base score changed	CVE-2026-65660	whole record microsoft	stated at publication 6.5, now states 8.8CVSS v3.1 · base scoreMediumHigh	Time to revision 16 days
Thu 20 Aug 2026· 2 changes
2026-08-20	CVSS base score changed	Show all 2 CVE records in this change: CVSS base score changed: 8.8 → 9.8Hide the 2 CVE records in this change: CVSS base score changed: 8.8 → 9.8	whole record microsoft	stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 37 days
2026-08-20	same kind of change as the line above	CVE-2026-54117	same vendor as the line above	same change as the line above	Time to revision 37 days
2026-08-20	same kind of change as the line above	CVE-2026-54118	same vendor as the line above	same change as the line above	Time to revision 37 days
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· 19 changes
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
2026-08-14	CVSS base score changed	CVE-2026-65796	whole record microsoft	stated at publication 5.9, now states 8.1CVSS v3.1 · base scoreMediumHigh	Time to revision 3 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· 1 change
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 3 Aug 2026· 2 changes
2026-08-03	CVSS base score changed	CVE-2026-47296	whole record microsoft	stated at publication 7.8, now states 7.5CVSS v3.1 · base scoreHighHigh	Time to revision 20 days
2026-08-03	CVSS base score changed	CVE-2026-55002	whole record microsoft	stated at publication 7.8, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 20 days
Tue 28 Jul 2026· 28 changes
2026-07-28	Fix version moved	Show all 7 CVE records in this change: Fix version moved: 15.01.2507.069 → 15.01.2507.071 from microsoftHide the 7 CVE records in this change: Fix version moved: 15.01.2507.069 → 15.01.2507.071 from microsoft	microsoftmicrosoft exchange server 2016 cumulative update 23	stated at publication 15.01.2507.069, now states 15.01.2507.071Release branch starts at 15.01.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45500	same vendor as the line above	same change as the line aboveRelease branch starts at 15.01.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45501	same vendor as the line above	same change as the line aboveRelease branch starts at 15.01.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45502	same vendor as the line above	same change as the line aboveRelease branch starts at 15.01.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45503	same vendor as the line above	same change as the line aboveRelease branch starts at 15.01.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45504	same vendor as the line above	same change as the line aboveRelease branch starts at 15.01.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45583	same vendor as the line above	same change as the line aboveRelease branch starts at 15.01.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-47631	same vendor as the line above	same change as the line aboveRelease branch starts at 15.01.0.0.	Time to revision 49 days
2026-07-28	Fix version moved	Show all 7 CVE records in this change: Fix version moved: 15.02.1544.041 → 15.02.1544.043 from microsoftHide the 7 CVE records in this change: Fix version moved: 15.02.1544.041 → 15.02.1544.043 from microsoft	microsoftmicrosoft exchange server 2019 cumulative update 14	stated at publication 15.02.1544.041, now states 15.02.1544.043Release branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45500	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45501	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45502	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45503	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45504	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45583	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-47631	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	Fix version moved	Show all 7 CVE records in this change: Fix version moved: 15.02.1748.046 → 15.02.1748.048 from microsoftHide the 7 CVE records in this change: Fix version moved: 15.02.1748.046 → 15.02.1748.048 from microsoft	microsoftmicrosoft exchange server 2019 cumulative update 15	stated at publication 15.02.1748.046, now states 15.02.1748.048Release branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45500	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45501	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45502	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45503	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45504	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45583	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-47631	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	Fix version moved	Show all 7 CVE records in this change: Fix version moved: 15.02.2562.043 → 15.02.2562.045 from microsoftHide the 7 CVE records in this change: Fix version moved: 15.02.2562.043 → 15.02.2562.045 from microsoft	microsoftmicrosoft exchange server subscription edition rtm	stated at publication 15.02.2562.043, now states 15.02.2562.045Release branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45500	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45501	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45502	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45503	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45504	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-45583	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
2026-07-28	same kind of change as the line above	CVE-2026-47631	same vendor as the line above	same change as the line aboveRelease branch starts at 15.02.0.0.	Time to revision 49 days
Sun 26 Jul 2026· 2 changes
2026-07-26	Product added	CVE-2026-48561Show all 2 products in this change: Product added: 2 products named as affected in CVE-2026-48561Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2026-48561	microsoft	not named as affected at publication, now names microsoft edge copilot for android and 1 more	Time to revision 12 days
2026-07-26	same kind of change as the line above	CVE-2026-48561	same vendor as the line above	not named as affected at publication, now names microsoft edge copilot for android	Time to revision 12 days
2026-07-26	same kind of change as the line above	CVE-2026-48561	same vendor as the line above	not named as affected at publication, now names microsoft edge copilot for ios	Time to revision 12 days
Wed 22 Jul 2026· 26 changes
2026-07-222 commits	Fix version moved	Show all 11 CVE records in this change: Fix version moved: 10.0.6 → 10.0.10 from microsoftHide the 11 CVE records in this change: Fix version moved: 10.0.6 → 10.0.10 from microsoft	microsoft.net 10.0	stated at publication 10.0.6, now states 10.0.10Branches and original-value intervals are stated on each row.	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50524	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.0.	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50525	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.0.	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50526	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.0.	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50527	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.0.	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50528	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.0.	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50648	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.0.	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50651	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.0.	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50659	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.0.	Time to revision 8 days
3 more rows in this change are not listed here. Open all 11 rows →
2026-07-22	Product added	CVE-2026-47304Show all 3 products in this change: Product added: 3 products named as affected in CVE-2026-47304Hide the 3 products in this change: Product added: 3 products named as affected in CVE-2026-47304	microsoft	not named as affected at publication, now names .net 10.0 and 2 more	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names .net 10.0	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names .net 8.0	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names .net 9.0	Time to revision 8 days
2026-07-22	Product added	Show all 12 CVE records in this change: Product added: microsoft .net framework 4.8.1 named as affected from microsoftHide the 12 CVE records in this change: Product added: microsoft .net framework 4.8.1 named as affected from microsoft	microsoft	not named as affected at publication, now names microsoft .net framework 4.8.1	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	same change as the line above	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50304	same vendor as the line above	same change as the line above	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50324	same vendor as the line above	same change as the line above	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50355	same vendor as the line above	same change as the line above	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50368	same vendor as the line above	same change as the line above	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50411	same vendor as the line above	same change as the line above	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50525	same vendor as the line above	same change as the line above	Time to revision 8 days
2026-07-22	same kind of change as the line above	CVE-2026-50647	same vendor as the line above	same change as the line above	Time to revision 8 days
4 more rows in this change are not listed here. Open all 12 rows →
Tue 21 Jul 2026· 3 changes
2026-07-21	Product added	CVE-2026-47304Show all 3 products in this change: Product added: 3 products named as affected in CVE-2026-47304Hide the 3 products in this change: Product added: 3 products named as affected in CVE-2026-47304	microsoft	not named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8) and 2 more	Time to revision 7 days
2026-07-21	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8)	Time to revision 7 days
2026-07-21	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10)	Time to revision 7 days
2026-07-21	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft visual studio 2026 version 18.5	Time to revision 7 days
Thu 16 Jul 2026· 42 changes
2026-07-16	Product added	Show all 8 CVE records in this change: Product added: 6 products named as affected from microsoftHide the 8 CVE records in this change: Product added: 6 products named as affected from microsoft42 rows, one per record and product	microsoft	not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 and 5 more	Time to revision 2 days
2026-07-16	same kind of change as the line above	CVE-2026-50304	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2	Time to revision 2 days
2026-07-16	same kind of change as the line above	CVE-2026-50304	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.8	Time to revision 2 days
2026-07-16	same kind of change as the line above	CVE-2026-50304	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1	Time to revision 2 days
2026-07-16	same kind of change as the line above	CVE-2026-50304	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2	Time to revision 2 days
2026-07-16	same kind of change as the line above	CVE-2026-50304	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 4.8	Time to revision 2 days
2026-07-16	same kind of change as the line above	CVE-2026-50324	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2	Time to revision 2 days
2026-07-16	same kind of change as the line above	CVE-2026-50324	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.8	Time to revision 2 days
2026-07-16	same kind of change as the line above	CVE-2026-50324	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1	Time to revision 2 days
34 more rows in this change are not listed here. Open all 42 rows →
Wed 15 Jul 2026· 24 changes
2026-07-15	Product added	Show all 4 CVE records in this change: Product added: 6 products named as affected from microsoftHide the 4 CVE records in this change: Product added: 6 products named as affected from microsoft24 rows, one per record and product	microsoft	not named as affected at publication, now names microsoft .net framework 3.5 and 5 more	Time to revision 1 days
2026-07-15	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5	Time to revision 1 days
2026-07-15	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2	Time to revision 1 days
2026-07-15	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.8	Time to revision 1 days
2026-07-15	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1	Time to revision 1 days
2026-07-15	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2	Time to revision 1 days
2026-07-15	same kind of change as the line above	CVE-2026-47304	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 4.8	Time to revision 1 days
2026-07-15	same kind of change as the line above	CVE-2026-50525	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5	Time to revision 1 days
2026-07-15	same kind of change as the line above	CVE-2026-50525	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2	Time to revision 1 days
16 more rows in this change are not listed here. Open all 24 rows →
Fri 19 Jun 2026· 1 change
2026-06-19	CVSS base score changed	CVE-2026-42915	whole record microsoft	stated at publication 5.7, now states 5.5CVSS v3.1 · base scoreMediumMedium	Time to revision 10 days
Mon 15 Jun 2026· 3 changes
2026-06-15	Fix version moved	Show all 3 CVE records in this change: Fix version moved: 1.123.1 → 1.123.2 from microsoftHide the 3 CVE records in this change: Fix version moved: 1.123.1 → 1.123.2 from microsoft	microsoftvisual studio code	stated at publication 1.123.1, now states 1.123.2Release branch starts at 1.0.0.	Time to revision 6 days
2026-06-15	same kind of change as the line above	CVE-2026-47287	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.	Time to revision 6 days
2026-06-15	same kind of change as the line above	CVE-2026-47281	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.	Time to revision 6 days
2026-06-15	same kind of change as the line above	CVE-2026-47284	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.	Time to revision 6 days
Wed 10 Jun 2026· 3 changes
2026-06-10	Fix version moved	Show all 2 CVE records in this change: Fix version moved: 1.119.1 → 1.123.2 from microsoftHide the 2 CVE records in this change: Fix version moved: 1.119.1 → 1.123.2 from microsoft	microsoftvisual studio code	stated at publication 1.119.1, now states 1.123.2Release branch starts at 1.0.0.	Time to revision 1 days
2026-06-10	same kind of change as the line above	CVE-2026-40376	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.	Time to revision 1 days
2026-06-10	same kind of change as the line above	CVE-2026-48569	same vendor as the line above	same change as the line aboveRelease branch starts at 1.0.0.	Time to revision 1 days
2026-06-10	Fix version moved	CVE-2026-45482	microsoftmicrosoft visual studio code copilot chat extension	stated at publication 1.123.1, now states 1.123.2Release branch starts at 0.27.0.	Time to revision 1 days
Tue 9 Jun 2026· 69 changes
2026-06-09	Fix version moved	Show all 53 CVE records in this change: Fix version moved: 10.0.19045.7291 → 10.0.19045.7417 from microsoftHide the 53 CVE records in this change: Fix version moved: 10.0.19045.7291 → 10.0.19045.7417 from microsoft	microsoftwindows 10 version 22h2	stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-21530	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-33834	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-33839	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-33841	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-34329	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-34330	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-34331	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-34333	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54	Time to revision 28 days
45 more rows in this change are not listed here. Open all 53 rows →
2026-06-09	Fix version moved	CVE-2026-32175	microsoftmicrosoft visual studio 2022 version 17.14	stated at publication 17.14.31, now states 17.14.32Release branch starts at 17.14.0.bulk ×54	Time to revision 28 days
2026-06-092 commits	Product added	Show all 7 CVE records in this change: Product added: 11 products named as affected from microsoftHide the 7 CVE records in this change: Product added: 11 products named as affected from microsoft15 rows, one per record and product	microsoft	not named as affected at publication, now names microsoft excel for android and 10 moreBranches and original-value intervals are stated on each row.	Time to revision 28 to 609 days
2026-06-09	same kind of change as the line above	CVE-2026-41100	same vendor as the line above	not named as affected at publication, now names microsoft excel for android	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-41100	same vendor as the line above	not named as affected at publication, now names microsoft loop for android	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-41100	same vendor as the line above	not named as affected at publication, now names microsoft onenote for android	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-41100	same vendor as the line above	not named as affected at publication, now names microsoft powerpoint for android	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2026-41100	same vendor as the line above	not named as affected at publication, now names microsoft word for android	Time to revision 28 days
2026-06-09	same kind of change as the line above	CVE-2024-43582	same vendor as the line above	not named as affected at publication, now names windows 11 version 26h1	Time to revision 609 days
2026-06-09	same kind of change as the line above	CVE-2024-49075	same vendor as the line above	not named as affected at publication, now names windows 11 version 26h1	Time to revision 546 days
2026-06-09	same kind of change as the line above	CVE-2024-49123	same vendor as the line above	not named as affected at publication, now names windows 11 version 26h1	Time to revision 546 days
7 more rows in this change are not listed here. Open all 15 rows →
Fri 5 Jun 2026· 1 change
2026-06-05	Fix version moved	CVE-2026-32177	microsoftmicrosoft visual studio 2022 version 17.14	stated at publication 17.14.31, now states 17.14.32Release branch starts at 17.14.0.	Time to revision 24 days
Fri 15 May 2026· 1 change
2026-05-15	Product added	CVE-2026-40379	microsoft	not named as affected at publication, now names microsoft entra	Time to revision 3 days
Thu 14 May 2026· 5 changes
2026-05-14	Product added	CVE-2026-35433Show all 5 products in this change: Product added: 5 products named as affected in CVE-2026-35433Hide the 5 products in this change: Product added: 5 products named as affected in CVE-2026-35433	microsoft	not named as affected at publication, now names microsoft .net framework 3.5 and 4 more	Time to revision 2 days
2026-05-14	same kind of change as the line above	CVE-2026-35433	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5	Time to revision 2 days
2026-05-14	same kind of change as the line above	CVE-2026-35433	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2	Time to revision 2 days
2026-05-14	same kind of change as the line above	CVE-2026-35433	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.8	Time to revision 2 days
2026-05-14	same kind of change as the line above	CVE-2026-35433	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1	Time to revision 2 days
2026-05-14	same kind of change as the line above	CVE-2026-35433	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 4.8	Time to revision 2 days
Wed 13 May 2026· 2 changes
2026-05-13	Fix version moved	Show all 2 CVE records in this change: Fix version moved: 9.1.44.15 → 9.1.45.11 from microsoftHide the 2 CVE records in this change: Fix version moved: 9.1.44.15 → 9.1.45.11 from microsoft	microsoftmicrosoft dynamics 365 (on-premises) version 9.1	stated at publication 9.1.44.15, now states 9.1.45.11Release branch starts at 9.0.same day	Time to revision 1 days
2026-05-13	same kind of change as the line above	CVE-2026-42898	same vendor as the line above	same change as the line aboveRelease branch starts at 9.0.same day	Time to revision 1 days
2026-05-13	same kind of change as the line above	CVE-2026-42833	same vendor as the line above	same change as the line aboveRelease branch starts at 9.0.same day	Time to revision 1 days
Mon 11 May 2026· 5 changes
2026-05-11	Fix version moved	CVE-2026-21523	microsoftvisual studio code	stated at publication 1.109.2, now states 1.110.1Release branch starts at 1.0.0.	Time to revision 90 days
2026-05-11	Fix version moved	CVE-2026-20841	microsoftwindows notepad	stated at publication 11.2510, now states 11.2512.26.0Release branch starts at 11.0.0.Original value first replaced 2026-03-12; this value first seen 2026-05-11.	Time to revision 30 days
2026-05-11	Product added	CVE-2026-32226Show all 3 products in this change: Product added: 3 products named as affected in CVE-2026-32226Hide the 3 products in this change: Product added: 3 products named as affected in CVE-2026-32226	microsoft	not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 and 2 more	Time to revision 27 days
2026-05-11	same kind of change as the line above	CVE-2026-32226	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2	Time to revision 27 days
2026-05-11	same kind of change as the line above	CVE-2026-32226	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 4.7.2	Time to revision 27 days
2026-05-11	same kind of change as the line above	CVE-2026-32226	same vendor as the line above	not named as affected at publication, now names microsoft .net framework 4.8.1	Time to revision 27 days
Tue 28 Apr 2026· 1 change
2026-04-28	Product added	CVE-2026-40372	microsoft	not named as affected at publication, now names microsoft visual studio 2026 version 18.5	Time to revision 7 days
Wed 22 Apr 2026· 2 changes
2026-04-22	Product added	CVE-2026-26171Show all 2 products in this change: Product added: 2 products named as affected in CVE-2026-26171Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2026-26171	microsoft	not named as affected at publication, now names powershell 7.5 and 1 more	Time to revision 8 days
2026-04-22	same kind of change as the line above	CVE-2026-26171	same vendor as the line above	not named as affected at publication, now names powershell 7.5	Time to revision 8 days
2026-04-22	same kind of change as the line above	CVE-2026-26171	same vendor as the line above	not named as affected at publication, now names powershell 7.6	Time to revision 8 days
Tue 21 Apr 2026· 1 change
2026-04-21	Product added	CVE-2026-32203	microsoft	not named as affected at publication, now names microsoft visual studio 2026 version 18.4	Time to revision 7 days
Wed 15 Apr 2026· 1 change
2026-04-15	Record state changed	CVE-2026-32187	whole record microsoft	stated at publication PUBLISHED, now states REJECTED	Time to revision 19 days
Fri 10 Apr 2026· 1 change
2026-04-10	Fix version moved	CVE-2026-21518	microsoftvisual studio code	stated at publication 1.109.2, now states 1.110.1Release branch starts at 1.0.0.	Time to revision 59 days
Wed 1 Apr 2026· 1 change
2026-04-01	CVSS base score changed	CVE-2026-20963	whole record microsoft	stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 78 days
Fri 27 Mar 2026· 1 change
2026-03-27	Product added	CVE-2026-26137	microsoft	not named as affected at publication, now names microsoft exchange online	Time to revision 8 days
Mon 23 Mar 2026· 3 changes
2026-03-23	Product added	CVE-2026-25166Show all 2 products in this change: Product added: 2 products named as affected in CVE-2026-25166Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2026-25166	microsoft	not named as affected at publication, now names windows adk for windows 10, version 2004 and 1 more	Time to revision 13 days
2026-03-23	same kind of change as the line above	CVE-2026-25166	same vendor as the line above	not named as affected at publication, now names windows adk for windows 10, version 2004	Time to revision 13 days
2026-03-23	same kind of change as the line above	CVE-2026-25166	same vendor as the line above	not named as affected at publication, now names windows adk for windows 11, version 22h2	Time to revision 13 days
2026-03-23	CVSS base score changed	CVE-2026-26137	whole record microsoft	stated at publication 8.9, now states 9.9CVSS v3.1 · base scoreHighCritical	Time to revision 4 days
Fri 13 Mar 2026· 23 changes
2026-03-133 commits	Product added	Show all 5 CVE records in this change: Product added: 11 products named as affected from microsoftHide the 5 CVE records in this change: Product added: 11 products named as affected from microsoft21 rows, one per record and product	microsoft	not named as affected at publication, now names windows 10 version 1607 and 10 moreBranches and original-value intervals are stated on each row.	Time to revision 3 to 31 days
2026-03-13	same kind of change as the line above	CVE-2026-25172	same vendor as the line above	not named as affected at publication, now names windows 10 version 1607	Time to revision 3 days
2026-03-13	same kind of change as the line above	CVE-2026-25172	same vendor as the line above	not named as affected at publication, now names windows 10 version 1809	Time to revision 3 days
2026-03-13	same kind of change as the line above	CVE-2026-25172	same vendor as the line above	not named as affected at publication, now names windows 10 version 21h2	Time to revision 3 days
2026-03-13	same kind of change as the line above	CVE-2026-25172	same vendor as the line above	not named as affected at publication, now names windows 10 version 22h2	Time to revision 3 days
2026-03-13	same kind of change as the line above	CVE-2026-25172	same vendor as the line above	not named as affected at publication, now names windows 11 version 22h3	Time to revision 3 days
2026-03-13	same kind of change as the line above	CVE-2026-25172	same vendor as the line above	not named as affected at publication, now names windows 11 version 23h2	Time to revision 3 days
2026-03-13	same kind of change as the line above	CVE-2026-25172	same vendor as the line above	not named as affected at publication, now names windows 11 version 24h2	Time to revision 3 days
2026-03-13	same kind of change as the line above	CVE-2026-25172	same vendor as the line above	not named as affected at publication, now names windows 11 version 25h2	Time to revision 3 days
13 more rows in this change are not listed here. Open all 21 rows →
2026-03-13	CVSS base score changed	Show all 2 CVE records in this change: CVSS base score changed: 8.8 → 8.0Hide the 2 CVE records in this change: CVSS base score changed: 8.8 → 8.0	whole record microsoft	stated at publication 8.8, now states 8.0CVSS v3.1 · base scoreHighHigh	Time to revision 3 days
2026-03-13	same kind of change as the line above	CVE-2026-25172	same vendor as the line above	same change as the line above	Time to revision 3 days
2026-03-13	same kind of change as the line above	CVE-2026-26111	same vendor as the line above	same change as the line above	Time to revision 3 days
Fri 27 Feb 2026· 2 changes
2026-02-272 commits	Product added	Show all 2 CVE records in this change: Product added: microsoft visual studio code copilot chat extension named as affected from microsoftHide the 2 CVE records in this change: Product added: microsoft visual studio code copilot chat extension named as affected from microsoft	microsoft	not named as affected at publication, now names microsoft visual studio code copilot chat extensionBranches and original-value intervals are stated on each row.	Time to revision 17 days
2026-02-27	same kind of change as the line above	CVE-2026-21523	same vendor as the line above	same change as the line above	Time to revision 17 days
2026-02-27	same kind of change as the line above	CVE-2026-21518	same vendor as the line above	same change as the line above	Time to revision 17 days
Mon 23 Feb 2026· 1 change
2026-02-23	CVSS base score changed	CVE-2026-21518	whole record microsoft	stated at publication 6.5, now states 8.8CVSS v3.1 · base scoreMediumHigh	Time to revision 13 days
Fri 13 Feb 2026· 4 changes
2026-02-13	Product added	CVE-2025-21264	microsoft	not named as affected at publication, now names microsoft visual studio code copilot chat extension	Time to revision 276 days
2026-02-13	Product added	CVE-2025-27488	microsoft	not named as affected at publication, now names windows hlk, version 1809	Time to revision 276 days
2026-02-13	Product added	CVE-2025-47733	microsoft	not named as affected at publication, now names microsoft power pages	Time to revision 281 days
2026-02-13	CVSS base score changed	CVE-2025-59213	whole record microsoft	stated at publication 8.4, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 122 days
Thu 12 Feb 2026· 1 change
2026-02-12	CVSS base score changed	CVE-2026-20841	whole record microsoft	stated at publication 8.8, now states 7.8CVSS v3.1 · base scoreHighHigh	Time to revision 2 days
Wed 11 Feb 2026· 1 change
2026-02-11	CVSS base score changed	CVE-2026-21517	whole record microsoft	stated at publication 7.0, now states 4.7CVSS v3.1 · base scoreHighMedium	Time to revision 0 days
Fri 12 Dec 2025· 1 change
2025-12-12	CVSS base score changed	CVE-2025-62468	whole record microsoft	stated at publication 4.4, now states 5.5CVSS v3.1 · base scoreMediumMedium	Time to revision 3 days
Tue 9 Dec 2025· 4 changes
2025-12-09	Fix version moved	CVE-2025-60710	microsoftwindows 11 version 25h2	stated at publication 10.0.26200.7171, now states 10.0.26200.7462Release branch starts at 10.0.26200.0.	Time to revision 28 days
2025-12-09	Product added	CVE-2025-60710Show all 3 products in this change: Product added: 3 products named as affected in CVE-2025-60710Hide the 3 products in this change: Product added: 3 products named as affected in CVE-2025-60710	microsoft	not named as affected at publication, now names windows 11 version 24h2 and 2 more	Time to revision 28 days
2025-12-09	same kind of change as the line above	CVE-2025-60710	same vendor as the line above	not named as affected at publication, now names windows 11 version 24h2	Time to revision 28 days
2025-12-09	same kind of change as the line above	CVE-2025-60710	same vendor as the line above	not named as affected at publication, now names windows server 2025	Time to revision 28 days
2025-12-09	same kind of change as the line above	CVE-2025-60710	same vendor as the line above	not named as affected at publication, now names windows server 2025 (server core installation)	Time to revision 28 days
Tue 25 Nov 2025· 1 change
2025-11-25	CVSS base score changed	CVE-2025-64660	whole record microsoft	stated at publication 5.7, now states 8.0CVSS v3.1 · base scoreMediumHigh	Time to revision 5 days
Sat 22 Nov 2025· 3 changes
2025-11-22	CVSS base score changed	Show all 3 CVE records in this change: CVSS base score changed: 6.5 → 9.3Hide the 3 CVE records in this change: CVSS base score changed: 6.5 → 9.3	whole record microsoft	stated at publication 6.5, now states 9.3CVSS v3.1 · base scoreMediumCritical	Time to revision 43 days
2025-11-22	same kind of change as the line above	CVE-2025-59252	same vendor as the line above	same change as the line above	Time to revision 43 days
2025-11-22	same kind of change as the line above	CVE-2025-59272	same vendor as the line above	same change as the line above	Time to revision 43 days
2025-11-22	same kind of change as the line above	CVE-2025-59286	same vendor as the line above	same change as the line above	Time to revision 43 days
Wed 12 Nov 2025· 6 changes
2025-11-12	Product added	Show all 3 CVE records in this change: Product added: 2 products named as affected from microsoftHide the 3 CVE records in this change: Product added: 2 products named as affected from microsoft6 rows, one per record and product	microsoft	not named as affected at publication, now names microsoft office ltsc for mac 2021 and 1 more	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-60726	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2021	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-60726	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2024	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-60727	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2021	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-60727	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2024	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-62203	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2021	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-62203	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2024	Time to revision 0 days
Fri 31 Oct 2025· 1 change
2025-10-31	CVSS base score changed	CVE-2025-59503	whole record microsoft	stated at publication 9.9, now states 10.0CVSS v3.1 · base scoreCriticalCritical	Time to revision 8 days
Thu 23 Oct 2025· 1 change
2025-10-23	CVSS base score changed	CVE-2025-55321	whole record microsoft	stated at publication 8.7, now states 9.3CVSS v3.1 · base scoreHighCritical	Time to revision 14 days
Fri 17 Oct 2025· 1 change
2025-10-17	CVSS base score changed	CVE-2025-55320	whole record microsoft	stated at publication 6.7, now states 6.8CVSS v3.1 · base scoreMediumMedium	Time to revision 3 days
Wed 15 Oct 2025· 3 changes
2025-10-15	Fix version moved	CVE-2025-58724	microsoftarc enabled servers - azure connected machine agent	stated at publication 1.56, now states 1.57Release branch starts at 1.0.0.	Time to revision 1 days
2025-10-15	Product added	CVE-2025-50173	microsoft	not named as affected at publication, now names multimedia redirection installer	Time to revision 64 days
2025-10-15	CVSS base score changed	CVE-2025-53132	whole record microsoft	stated at publication 8.0, now states 7.8CVSS v3.1 · base scoreHighHigh	Time to revision 64 days
Thu 18 Sep 2025· 1 change
2025-09-18	CVSS base score changed	CVE-2025-55241	whole record microsoft	stated at publication 9.0, now states 10.0CVSS v3.1 · base scoreCriticalCritical	Time to revision 14 days
Wed 17 Sep 2025· 1 change
2025-09-17	CVSS base score changed	CVE-2025-50154	whole record microsoft	stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium	Time to revision 36 days
Thu 11 Sep 2025· 2 changes
2025-09-11	Product added	CVE-2025-49734Show all 2 products in this change: Product added: 2 products named as affected in CVE-2025-49734Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2025-49734	microsoft	not named as affected at publication, now names powershell 7.4 and 1 more	Time to revision 2 days
2025-09-11	same kind of change as the line above	CVE-2025-49734	same vendor as the line above	not named as affected at publication, now names powershell 7.4	Time to revision 2 days
2025-09-11	same kind of change as the line above	CVE-2025-49734	same vendor as the line above	not named as affected at publication, now names powershell 7.5	Time to revision 2 days
Tue 9 Sep 2025· 16 changes
2025-09-09	Fix version moved	CVE-2025-21293Show all 3 products in this change: Fix version moved: 10.0.26100.2894 → 10.0.26100.6584 in CVE-2025-21293Hide the 3 products in this change: Fix version moved: 10.0.26100.2894 → 10.0.26100.6584 in CVE-2025-21293	microsoft3 products	stated at publication 10.0.26100.2894, now states 10.0.26100.6584Release branch starts at 10.0.26100.0.	Time to revision 238 days
2025-09-09	same kind of change as the line above	CVE-2025-21293	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 238 days
2025-09-09	same kind of change as the line above	CVE-2025-21293	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 238 days
2025-09-09	same kind of change as the line above	CVE-2025-21293	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 238 days
2025-09-09	Fix version moved	CVE-2025-48807Show all 3 products in this change: Fix version moved: 10.0.14393.8246 → 10.0.14393.8422 in CVE-2025-48807Hide the 3 products in this change: Fix version moved: 10.0.14393.8246 → 10.0.14393.8422 in CVE-2025-48807	microsoft3 products	stated at publication 10.0.14393.8246, now states 10.0.14393.8422Release branch starts at 10.0.14393.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.14393.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.14393.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.14393.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807Show all 3 products in this change: Fix version moved: 10.0.17763.7558 → 10.0.17763.7792 in CVE-2025-48807Hide the 3 products in this change: Fix version moved: 10.0.17763.7558 → 10.0.17763.7792 in CVE-2025-48807	microsoft3 products	stated at publication 10.0.17763.7558, now states 10.0.17763.7792Release branch starts at 10.0.17763.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.17763.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.17763.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.17763.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807	microsoftwindows 10 version 21h2	stated at publication 10.0.19044.6093, now states 10.0.19044.6332Release branch starts at 10.0.19044.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807	microsoftwindows 11 version 22h2	stated at publication 10.0.22621.5624, now states 10.0.22621.5909Release branch starts at 10.0.22621.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807Show all 3 products in this change: Fix version moved: 10.0.26100.4652 → 10.0.26100.6584 in CVE-2025-48807Hide the 3 products in this change: Fix version moved: 10.0.26100.4652 → 10.0.26100.6584 in CVE-2025-48807	microsoft3 products	stated at publication 10.0.26100.4652, now states 10.0.26100.6584Release branch starts at 10.0.26100.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807	microsoftwindows server 2022	stated at publication 10.0.20348.3932, now states 10.0.20348.4171Release branch starts at 10.0.20348.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807	microsoftwindows server 2022, 23h2 edition (server core installation)	stated at publication 10.0.25398.1732, now states 10.0.25398.1849Release branch starts at 10.0.25398.0.	Time to revision 28 days
Thu 21 Aug 2025· 1 change
2025-08-21	CVSS base score changed	CVE-2025-48807	whole record microsoft	stated at publication 7.5, now states 6.7CVSS v3.1 · base scoreHighMedium	Time to revision 9 days
Fri 15 Aug 2025· 6 changes
2025-08-15	Product added	CVE-2025-50171Show all 6 products in this change: Product added: 6 products named as affected in CVE-2025-50171Hide the 6 products in this change: Product added: 6 products named as affected in CVE-2025-50171	microsoft	not named as affected at publication, now names windows 10 version 21h2 and 5 more	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 10 version 21h2	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 10 version 22h2	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 11 version 22h2	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 11 version 22h3	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 11 version 23h2	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 11 version 24h2	Time to revision 3 days
Tue 12 Aug 2025· 1 change
2025-08-12	Fix version moved	CVE-2025-53729	microsoftazure file sync	stated at publication 18.0.0.0, now states 18.3.0.0Release branch starts at 1.0.0.same day	Time to revision 0 days
Tue 22 Jul 2025· 2 changes
2025-07-22	CVSS base score changed	Show all 2 CVE records in this change: CVSS base score changed: 6.3 → 6.5Hide the 2 CVE records in this change: CVSS base score changed: 6.3 → 6.5	whole record microsoft	stated at publication 6.3, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2025-07-21; this value first seen 2025-07-22.	Time to revision 1 to 13 days
2025-07-22	same kind of change as the line above	CVE-2025-49706	same vendor as the line above	same change as the line aboveOriginal value first replaced 2025-07-21; this value first seen 2025-07-22.	Time to revision 13 days
2025-07-22	same kind of change as the line above	CVE-2025-53771	same vendor as the line above	same change as the line aboveOriginal value first replaced 2025-07-21; this value first seen 2025-07-22.	Time to revision 1 days
Tue 15 Jul 2025· 1 change
2025-07-15	CVSS base score changed	CVE-2025-49716	whole record microsoft	stated at publication 5.9, now states 7.5CVSS v3.1 · base scoreMediumHigh	Time to revision 7 days
Fri 11 Jul 2025· 2 changes
2025-07-11	Fix version moved	CVE-2025-47956	microsoftwindows security app	stated at publication 1000.27840.0.1000, now states 1000.27840.1000.0Release branch starts at 1000.0.0.0.	Time to revision 31 days
2025-07-11	CVSS base score changed	CVE-2025-49670	whole record microsoft	stated at publication 8.8, now states 6.5CVSS v3.1 · base scoreHighMedium	Time to revision 3 days
Tue 8 Jul 2025· 4 changes
2025-07-08	Fix version moved	CVE-2024-49000	microsoftmicrosoft sql server 2016 service pack 3 (gdr)	stated at publication 13.0.6455.2, now states 13.0.6460.7Release branch starts at 13.0.0.	Time to revision 238 days
2025-07-08	Fix version moved	CVE-2024-49000	microsoftmicrosoft sql server 2016 service pack 3 azure connect feature pack	stated at publication 13.0.7050.2, now states 13.0.7055.9Release branch starts at 13.0.0.	Time to revision 238 days
2025-07-08	Product added	CVE-2025-30399Show all 2 products in this change: Product added: 2 products named as affected in CVE-2025-30399Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2025-30399	microsoft	not named as affected at publication, now names powershell 7.4 and 1 more	Time to revision 26 days
2025-07-08	same kind of change as the line above	CVE-2025-30399	same vendor as the line above	not named as affected at publication, now names powershell 7.4	Time to revision 26 days
2025-07-08	same kind of change as the line above	CVE-2025-30399	same vendor as the line above	not named as affected at publication, now names powershell 7.5	Time to revision 26 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 →