Skip to content

Product added

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

366 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "Product added" from 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.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 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.
Thu 3 Sep 2026· 1 record change
2026-09-03CVE-2026-58641not named as affected at publication, now names skiasharpDays to revision 23
Fri 28 Aug 2026· 1 record change
2026-08-28CVE-2026-59133not named as affected at publication, now names microsoft hpc pack 2019Days to revision 17
Sun 16 Aug 2026· 1 record change
2026-08-16CVE-2026-59124not named as affected at publication, now names microsoft hpc pack 2019Days to revision 5
Thu 13 Aug 2026· 25 record changes
2026-08-13not named as affected at publication, now names office online serverDays to revision 2
2026-08-13CVE-2026-65807same vendor as the line abovesame change as the line aboveDays to revision 2
2026-08-13CVE-2026-68793same vendor as the line abovesame change as the line aboveDays to revision 2
2026-08-13CVE-2026-68794same vendor as the line abovesame change as the line aboveDays to revision 2
2026-08-13CVE-2026-68795same vendor as the line abovesame change as the line aboveDays to revision 2
2026-08-13CVE-2026-68796same vendor as the line abovesame change as the line aboveDays to revision 2
2026-08-13CVE-2026-68797same vendor as the line abovesame change as the line aboveDays to revision 2
2026-08-13CVE-2026-68799same vendor as the line abovesame change as the line aboveDays to revision 2
2026-08-13CVE-2026-68800same vendor as the line abovesame change as the line aboveDays to revision 2
17 more rows in this change are not listed here. Open all 25 rows
Tue 11 Aug 2026· 1 record change
2026-08-11CVE-2026-59118not named as affected at publication, now names copilot coworkDays to revision 5
Sun 26 Jul 2026· 2 record changes
2026-07-26CVE-2026-48561not named as affected at publication, now names microsoft edge copilot for android and 1 moreDays to revision 12
2026-07-26CVE-2026-48561same vendor as the line abovenot named as affected at publication, now names microsoft edge copilot for androidDays to revision 12
2026-07-26CVE-2026-48561same vendor as the line abovenot named as affected at publication, now names microsoft edge copilot for iosDays to revision 12
Wed 22 Jul 2026· 15 record changes
2026-07-22CVE-2026-47304not named as affected at publication, now names .net 10.0 and 2 moreDays to revision 8
2026-07-22CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names .net 10.0Days to revision 8
2026-07-22CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names .net 8.0Days to revision 8
2026-07-22CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names .net 9.0Days to revision 8
2026-07-22not named as affected at publication, now names microsoft .net framework 4.8.1Days to revision 8
2026-07-22CVE-2026-47304same vendor as the line abovesame change as the line aboveDays to revision 8
2026-07-22CVE-2026-50304same vendor as the line abovesame change as the line aboveDays to revision 8
2026-07-22CVE-2026-50324same vendor as the line abovesame change as the line aboveDays to revision 8
2026-07-22CVE-2026-50355same vendor as the line abovesame change as the line aboveDays to revision 8
2026-07-22CVE-2026-50368same vendor as the line abovesame change as the line aboveDays to revision 8
2026-07-22CVE-2026-50411same vendor as the line abovesame change as the line aboveDays to revision 8
2026-07-22CVE-2026-50525same vendor as the line abovesame change as the line aboveDays to revision 8
2026-07-22CVE-2026-50647same vendor as the line abovesame change as the line aboveDays to revision 8
4 more rows in this change are not listed here. Open all 12 rows
Tue 21 Jul 2026· 3 record changes
2026-07-21CVE-2026-47304not named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8) and 2 moreDays to revision 7
2026-07-21CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8)Days to revision 7
2026-07-21CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10)Days to revision 7
2026-07-21CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2026 version 18.5Days to revision 7
Thu 16 Jul 2026· 42 record changes
2026-07-1642 rows, one per record and productnot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 and 5 moreDays to revision 2
2026-07-16CVE-2026-50304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2Days to revision 2
2026-07-16CVE-2026-50304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8Days to revision 2
2026-07-16CVE-2026-50304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1Days to revision 2
2026-07-16CVE-2026-50304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2Days to revision 2
2026-07-16CVE-2026-50304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.8Days to revision 2
2026-07-16CVE-2026-50324same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2Days to revision 2
2026-07-16CVE-2026-50324same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8Days to revision 2
2026-07-16CVE-2026-50324same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1Days to revision 2
34 more rows in this change are not listed here. Open all 42 rows
Wed 15 Jul 2026· 24 record changes
2026-07-1524 rows, one per record and productnot named as affected at publication, now names microsoft .net framework 3.5 and 5 moreDays to revision 1
2026-07-15CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5Days to revision 1
2026-07-15CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2Days to revision 1
2026-07-15CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8Days to revision 1
2026-07-15CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1Days to revision 1
2026-07-15CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2Days to revision 1
2026-07-15CVE-2026-47304same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.8Days to revision 1
2026-07-15CVE-2026-50525same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5Days to revision 1
2026-07-15CVE-2026-50525same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2Days to revision 1
16 more rows in this change are not listed here. Open all 24 rows
Tue 9 Jun 2026· 15 record changes
2026-06-092 commits15 rows, one per record and productnot named as affected at publication, now names microsoft excel for android and 10 moreBranches and original-value intervals are stated on each row.Days to revision 28 to 609
2026-06-09CVE-2026-41100same vendor as the line abovenot named as affected at publication, now names microsoft excel for androidDays to revision 28
2026-06-09CVE-2026-41100same vendor as the line abovenot named as affected at publication, now names microsoft loop for androidDays to revision 28
2026-06-09CVE-2026-41100same vendor as the line abovenot named as affected at publication, now names microsoft onenote for androidDays to revision 28
2026-06-09CVE-2026-41100same vendor as the line abovenot named as affected at publication, now names microsoft powerpoint for androidDays to revision 28
2026-06-09CVE-2026-41100same vendor as the line abovenot named as affected at publication, now names microsoft word for androidDays to revision 28
2026-06-09CVE-2024-43582same vendor as the line abovenot named as affected at publication, now names windows 11 version 26h1Days to revision 609
2026-06-09CVE-2024-49075same vendor as the line abovenot named as affected at publication, now names windows 11 version 26h1Days to revision 546
2026-06-09CVE-2024-49123same vendor as the line abovenot named as affected at publication, now names windows 11 version 26h1Days to revision 546
7 more rows in this change are not listed here. Open all 15 rows
Fri 15 May 2026· 1 record change
2026-05-15CVE-2026-40379not named as affected at publication, now names microsoft entraDays to revision 3
Thu 14 May 2026· 5 record changes
2026-05-14CVE-2026-35433not named as affected at publication, now names microsoft .net framework 3.5 and 4 moreDays to revision 2
2026-05-14CVE-2026-35433same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5Days to revision 2
2026-05-14CVE-2026-35433same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2Days to revision 2
2026-05-14CVE-2026-35433same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8Days to revision 2
2026-05-14CVE-2026-35433same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1Days to revision 2
2026-05-14CVE-2026-35433same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.8Days to revision 2
Mon 11 May 2026· 3 record changes
2026-05-11CVE-2026-32226not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 and 2 moreDays to revision 27
2026-05-11CVE-2026-32226same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2Days to revision 27
2026-05-11CVE-2026-32226same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.7.2Days to revision 27
2026-05-11CVE-2026-32226same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 4.8.1Days to revision 27
Tue 28 Apr 2026· 1 record change
2026-04-28CVE-2026-40372not named as affected at publication, now names microsoft visual studio 2026 version 18.5Days to revision 7
Wed 22 Apr 2026· 2 record changes
2026-04-22CVE-2026-26171not named as affected at publication, now names powershell 7.5 and 1 moreDays to revision 8
2026-04-22CVE-2026-26171same vendor as the line abovenot named as affected at publication, now names powershell 7.5Days to revision 8
2026-04-22CVE-2026-26171same vendor as the line abovenot named as affected at publication, now names powershell 7.6Days to revision 8
Tue 21 Apr 2026· 1 record change
2026-04-21CVE-2026-32203not named as affected at publication, now names microsoft visual studio 2026 version 18.4Days to revision 7
Fri 27 Mar 2026· 1 record change
2026-03-27CVE-2026-26137not named as affected at publication, now names microsoft exchange onlineDays to revision 8
Mon 23 Mar 2026· 2 record changes
2026-03-23CVE-2026-25166not named as affected at publication, now names windows adk for windows 10, version 2004 and 1 moreDays to revision 13
2026-03-23CVE-2026-25166same vendor as the line abovenot named as affected at publication, now names windows adk for windows 10, version 2004Days to revision 13
2026-03-23CVE-2026-25166same vendor as the line abovenot named as affected at publication, now names windows adk for windows 11, version 22h2Days to revision 13
Fri 13 Mar 2026· 21 record changes
2026-03-133 commits21 rows, one per record and productnot named as affected at publication, now names windows 10 version 1607 and 10 moreBranches and original-value intervals are stated on each row.Days to revision 3 to 31
2026-03-13CVE-2026-25172same vendor as the line abovenot named as affected at publication, now names windows 10 version 1607Days to revision 3
2026-03-13CVE-2026-25172same vendor as the line abovenot named as affected at publication, now names windows 10 version 1809Days to revision 3
2026-03-13CVE-2026-25172same vendor as the line abovenot named as affected at publication, now names windows 10 version 21h2Days to revision 3
2026-03-13CVE-2026-25172same vendor as the line abovenot named as affected at publication, now names windows 10 version 22h2Days to revision 3
2026-03-13CVE-2026-25172same vendor as the line abovenot named as affected at publication, now names windows 11 version 22h3Days to revision 3
2026-03-13CVE-2026-25172same vendor as the line abovenot named as affected at publication, now names windows 11 version 23h2Days to revision 3
2026-03-13CVE-2026-25172same vendor as the line abovenot named as affected at publication, now names windows 11 version 24h2Days to revision 3
2026-03-13CVE-2026-25172same vendor as the line abovenot named as affected at publication, now names windows 11 version 25h2Days to revision 3
13 more rows in this change are not listed here. Open all 21 rows
Fri 27 Feb 2026· 2 record changes
2026-02-272 commitsnot named as affected at publication, now names microsoft visual studio code copilot chat extensionBranches and original-value intervals are stated on each row.Days to revision 17
2026-02-27CVE-2026-21523same vendor as the line abovesame change as the line aboveDays to revision 17
2026-02-27CVE-2026-21518same vendor as the line abovesame change as the line aboveDays to revision 17
Fri 13 Feb 2026· 3 record changes
2026-02-13CVE-2025-21264not named as affected at publication, now names microsoft visual studio code copilot chat extensionDays to revision 276
2026-02-13CVE-2025-27488not named as affected at publication, now names windows hlk, version 1809Days to revision 276
2026-02-13CVE-2025-47733not named as affected at publication, now names microsoft power pagesDays to revision 281
Tue 9 Dec 2025· 3 record changes
2025-12-09CVE-2025-60710not named as affected at publication, now names windows 11 version 24h2 and 2 moreDays to revision 28
2025-12-09CVE-2025-60710same vendor as the line abovenot named as affected at publication, now names windows 11 version 24h2Days to revision 28
2025-12-09CVE-2025-60710same vendor as the line abovenot named as affected at publication, now names windows server 2025Days to revision 28
2025-12-09CVE-2025-60710same vendor as the line abovenot named as affected at publication, now names windows server 2025 (server core installation)Days to revision 28
Wed 12 Nov 2025· 6 record changes
2025-11-126 rows, one per record and productnot named as affected at publication, now names microsoft office ltsc for mac 2021 and 1 moreDays to revision 0
2025-11-12CVE-2025-60726same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2021Days to revision 0
2025-11-12CVE-2025-60726same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2024Days to revision 0
2025-11-12CVE-2025-60727same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2021Days to revision 0
2025-11-12CVE-2025-60727same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2024Days to revision 0
2025-11-12CVE-2025-62203same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2021Days to revision 0
2025-11-12CVE-2025-62203same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2024Days to revision 0
Wed 15 Oct 2025· 1 record change
2025-10-15CVE-2025-50173not named as affected at publication, now names multimedia redirection installerDays to revision 64
Thu 11 Sep 2025· 2 record changes
2025-09-11CVE-2025-49734not named as affected at publication, now names powershell 7.4 and 1 moreDays to revision 2
2025-09-11CVE-2025-49734same vendor as the line abovenot named as affected at publication, now names powershell 7.4Days to revision 2
2025-09-11CVE-2025-49734same vendor as the line abovenot named as affected at publication, now names powershell 7.5Days to revision 2
Fri 15 Aug 2025· 6 record changes
2025-08-15CVE-2025-50171not named as affected at publication, now names windows 10 version 21h2 and 5 moreDays to revision 3
2025-08-15CVE-2025-50171same vendor as the line abovenot named as affected at publication, now names windows 10 version 21h2Days to revision 3
2025-08-15CVE-2025-50171same vendor as the line abovenot named as affected at publication, now names windows 10 version 22h2Days to revision 3
2025-08-15CVE-2025-50171same vendor as the line abovenot named as affected at publication, now names windows 11 version 22h2Days to revision 3
2025-08-15CVE-2025-50171same vendor as the line abovenot named as affected at publication, now names windows 11 version 22h3Days to revision 3
2025-08-15CVE-2025-50171same vendor as the line abovenot named as affected at publication, now names windows 11 version 23h2Days to revision 3
2025-08-15CVE-2025-50171same vendor as the line abovenot named as affected at publication, now names windows 11 version 24h2Days to revision 3
Tue 8 Jul 2025· 2 record changes
2025-07-08CVE-2025-30399not named as affected at publication, now names powershell 7.4 and 1 moreDays to revision 26
2025-07-08CVE-2025-30399same vendor as the line abovenot named as affected at publication, now names powershell 7.4Days to revision 26
2025-07-08CVE-2025-30399same vendor as the line abovenot named as affected at publication, now names powershell 7.5Days to revision 26
Mon 16 Jun 2025· 1 record change
2025-06-16CVE-2024-38179not named as affected at publication, now names azure stack os hciDays to revision 250
Thu 15 May 2025· 20 record changes
2025-05-152 commits20 rows, one per record and productnot named as affected at publication, now names microsoft office ltsc for mac 2021 and 5 moreBranches and original-value intervals are stated on each row.Days to revision 2
2025-05-15CVE-2025-29977same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2021Days to revision 2
2025-05-15CVE-2025-29977same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2024Days to revision 2
2025-05-15CVE-2025-29979same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2021Days to revision 2
2025-05-15CVE-2025-29979same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2024Days to revision 2
2025-05-15CVE-2025-30375same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2021Days to revision 2
2025-05-15CVE-2025-30375same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2024Days to revision 2
2025-05-15CVE-2025-30379same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2021Days to revision 2
2025-05-15CVE-2025-30379same vendor as the line abovenot named as affected at publication, now names microsoft office ltsc for mac 2024Days to revision 2
12 more rows in this change are not listed here. Open all 20 rows
Tue 11 Mar 2025· 3 record changes
2025-03-11CVE-2024-30098not named as affected at publication, now names windows 11 version 24h2 and 2 moreDays to revision 245
2025-03-11CVE-2024-30098same vendor as the line abovenot named as affected at publication, now names windows 11 version 24h2Days to revision 245
2025-03-11CVE-2024-30098same vendor as the line abovenot named as affected at publication, now names windows server 2025Days to revision 245
2025-03-11CVE-2024-30098same vendor as the line abovenot named as affected at publication, now names windows server 2025 (server core installation)Days to revision 245
Fri 14 Feb 2025· 1 record change
2025-02-14CVE-2025-21178not named as affected at publication, now names microsoft visual studio 2015 update 3Days to revision 31
Tue 11 Feb 2025· 5 record changes
2025-02-11CVE-2023-24932not named as affected at publication, now names windows 11 version 24h2 and 2 moreDays to revision 644
2025-02-11CVE-2023-24932same vendor as the line abovenot named as affected at publication, now names windows 11 version 24h2Days to revision 644
2025-02-11CVE-2023-24932same vendor as the line abovenot named as affected at publication, now names windows server 2025Days to revision 644
2025-02-11CVE-2023-24932same vendor as the line abovenot named as affected at publication, now names windows server 2025 (server core installation)Days to revision 644
2025-02-112 commitsnot named as affected at publication, now names microsoft visual studio 2015 update 3Branches and original-value intervals are stated on each row.Days to revision 28
2025-02-11CVE-2025-21172same vendor as the line abovesame change as the line aboveDays to revision 28
2025-02-11CVE-2025-21176same vendor as the line abovesame change as the line aboveDays to revision 28
Wed 29 Jan 2025· 4 record changes
2025-01-293 commitsnot named as affected at publication, now names powershell 7.5Branches and original-value intervals are stated on each row.Days to revision 15 to 113
2025-01-29CVE-2024-43485same vendor as the line abovesame change as the line aboveDays to revision 113
2025-01-29CVE-2024-43498same vendor as the line abovesame change as the line aboveDays to revision 78
2025-01-29CVE-2024-43499same vendor as the line abovesame change as the line aboveDays to revision 78
2025-01-29CVE-2025-21171same vendor as the line abovesame change as the line aboveDays to revision 15
Tue 31 Dec 2024· 1 record change
2024-12-31CVE-2024-35264not named as affected at publication, now names .net 6.0Days to revision 175
Fri 27 Dec 2024· 1 record change
2024-12-27CVE-2024-30077not named as affected at publication, now names windows 11 version 24h2Days to revision 199
Fri 20 Dec 2024· 3 record changes
2024-12-20CVE-2024-43594not named as affected at publication, now names microsoft system center 2019 and 2 moreDays to revision 10
2024-12-20CVE-2024-43594same vendor as the line abovenot named as affected at publication, now names microsoft system center 2019Days to revision 10
2024-12-20CVE-2024-43594same vendor as the line abovenot named as affected at publication, now names microsoft system center 2022Days to revision 10
2024-12-20CVE-2024-43594same vendor as the line abovenot named as affected at publication, now names microsoft system center 2025Days to revision 10
Tue 10 Dec 2024· 2 record changes
2024-12-10CVE-2024-43583not named as affected at publication, now names windows server 2025 and 1 moreDays to revision 63
2024-12-10CVE-2024-43583same vendor as the line abovenot named as affected at publication, now names windows server 2025Days to revision 63
2024-12-10CVE-2024-43583same vendor as the line abovenot named as affected at publication, now names windows server 2025 (server core installation)Days to revision 63
Wed 23 Oct 2024· 6 record changes
2024-10-236 rows, one per record and productnot named as affected at publication, now names powershell 7.2 and 1 moreDays to revision 15
2024-10-23CVE-2024-43483same vendor as the line abovenot named as affected at publication, now names powershell 7.2Days to revision 15
2024-10-23CVE-2024-43483same vendor as the line abovenot named as affected at publication, now names powershell 7.4Days to revision 15
2024-10-23CVE-2024-43484same vendor as the line abovenot named as affected at publication, now names powershell 7.2Days to revision 15
2024-10-23CVE-2024-43484same vendor as the line abovenot named as affected at publication, now names powershell 7.4Days to revision 15
2024-10-23CVE-2024-43485same vendor as the line abovenot named as affected at publication, now names powershell 7.2Days to revision 15
2024-10-23CVE-2024-43485same vendor as the line abovenot named as affected at publication, now names powershell 7.4Days to revision 15
Tue 8 Oct 2024· 2 record changes
2024-10-08CVE-2024-37341not named as affected at publication, now names microsoft sql server 2022 for (cu 15)Days to revision 28
2024-10-08CVE-2024-38095not named as affected at publication, now names .net 6.0Days to revision 91
Tue 10 Sep 2024· 15 record changes
2024-09-10CVE-2024-38138not named as affected at publication, now names windows server 2008 service pack 2 and 8 moreDays to revision 28
2024-09-10CVE-2024-38138same vendor as the line abovenot named as affected at publication, now names windows server 2008 service pack 2Days to revision 28
2024-09-10CVE-2024-38138same vendor as the line abovenot named as affected at publication, now names windows server 2008 r2 service pack 1Days to revision 28
2024-09-10CVE-2024-38138same vendor as the line abovenot named as affected at publication, now names windows server 2008 r2 service pack 1 (server core installation)Days to revision 28
2024-09-10CVE-2024-38138same vendor as the line abovenot named as affected at publication, now names windows server 2008 service pack 2Days to revision 28
2024-09-10CVE-2024-38138same vendor as the line abovenot named as affected at publication, now names windows server 2008 service pack 2 (server core installation)Days to revision 28
2024-09-10CVE-2024-38138same vendor as the line abovenot named as affected at publication, now names windows server 2012Days to revision 28
2024-09-10CVE-2024-38138same vendor as the line abovenot named as affected at publication, now names windows server 2012 (server core installation)Days to revision 28
2024-09-10CVE-2024-38138same vendor as the line abovenot named as affected at publication, now names windows server 2012 r2Days to revision 28
1 more row in this change is not listed here. Open all 9 rows
2024-09-10CVE-2024-35272not named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8) and 5 moreDays to revision 63
2024-09-10CVE-2024-35272same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8)Days to revision 63
2024-09-10CVE-2024-35272same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10)Days to revision 63
2024-09-10CVE-2024-35272same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2022 version 17.10Days to revision 63
2024-09-10CVE-2024-35272same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2022 version 17.11Days to revision 63
2024-09-10CVE-2024-35272same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2022 version 17.6Days to revision 63
2024-09-10CVE-2024-35272same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2022 version 17.8Days to revision 63
Thu 25 Jul 2024· 4 record changes
2024-07-25not named as affected at publication, now names powershell 7.4Days to revision 16
2024-07-25CVE-2024-30105same vendor as the line abovesame change as the line aboveDays to revision 16
2024-07-25CVE-2024-38095same vendor as the line abovesame change as the line aboveDays to revision 16
2024-07-25CVE-2024-38081not named as affected at publication, now names .net 6.0Days to revision 16
2024-07-25CVE-2024-38095not named as affected at publication, now names powershell 7.2Days to revision 16
Wed 19 Jun 2024· 1 record change
2024-06-19CVE-2024-30045not named as affected at publication, now names powershell 7.4Days to revision 36
Wed 15 May 2024· 2 record changes
2024-05-15CVE-2024-30046not named as affected at publication, now names .net 7.0 and 1 moreDays to revision 1
2024-05-15CVE-2024-30046same vendor as the line abovenot named as affected at publication, now names .net 7.0Days to revision 1
2024-05-15CVE-2024-30046same vendor as the line abovenot named as affected at publication, now names .net 8.0Days to revision 1
Tue 16 Apr 2024· 7 record changes
2024-04-16CVE-2024-21409not named as affected at publication, now names powershell 7.2Days to revision 7
2024-04-162 commitsnot named as affected at publication, now names powershell 7.3Branches and original-value intervals are stated on each row.Days to revision 7 to 35
2024-04-16CVE-2024-21409same vendor as the line abovesame change as the line aboveDays to revision 7
2024-04-16CVE-2024-21392same vendor as the line abovesame change as the line aboveDays to revision 35
2024-04-16CVE-2024-26190same vendor as the line abovesame change as the line aboveDays to revision 35
2024-04-162 commitsnot named as affected at publication, now names powershell 7.4Branches and original-value intervals are stated on each row.Days to revision 7 to 35
2024-04-16CVE-2024-21409same vendor as the line abovesame change as the line aboveDays to revision 7
2024-04-16CVE-2024-21392same vendor as the line abovesame change as the line aboveDays to revision 35
2024-04-16CVE-2024-26190same vendor as the line abovesame change as the line aboveDays to revision 35
Thu 11 Apr 2024· 1 record change
2024-04-11CVE-2024-21330not named as affected at publication, now names azure hdinsightDays to revision 30
Tue 9 Apr 2024· 3 record changes
2024-04-09CVE-2023-24932not named as affected at publication, now names windows 11 version 22h3 and 2 moreDays to revision 336
2024-04-09CVE-2023-24932same vendor as the line abovenot named as affected at publication, now names windows 11 version 22h3Days to revision 336
2024-04-09CVE-2023-24932same vendor as the line abovenot named as affected at publication, now names windows 11 version 23h2Days to revision 336
2024-04-09CVE-2023-24932same vendor as the line abovenot named as affected at publication, now names windows server 2022, 23h2 edition (server core installation)Days to revision 336
Fri 22 Mar 2024· 6 record changes
2024-03-22CVE-2024-0057not named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10) and 4 moreDays to revision 73
2024-03-22CVE-2024-0057same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10)Days to revision 73
2024-03-22CVE-2024-0057same vendor as the line abovenot named as affected at publication, now names nuget 17.4.0Days to revision 73
2024-03-22CVE-2024-0057same vendor as the line abovenot named as affected at publication, now names nuget 17.6.0Days to revision 73
2024-03-22CVE-2024-0057same vendor as the line abovenot named as affected at publication, now names nuget 17.8.0Days to revision 73
2024-03-22CVE-2024-0057same vendor as the line abovenot named as affected at publication, now names nuget 5.11.0Days to revision 73
2024-03-22CVE-2024-20677not named as affected at publication, now names 3d viewerDays to revision 73
Tue 19 Mar 2024· 1 record change
2024-03-19CVE-2024-2169certccnot named as affected at publication, now names wdsDays to revision 0
Fri 15 Mar 2024· 1 record change
2024-03-15CVE-2024-26163not named as affected at publication, now names microsoft edge (chromium-based) extended stableDays to revision 1
Tue 12 Mar 2024· 2 record changes
2024-03-12not named as affected at publication, now names microsoft visio 2016Days to revision 217
2024-03-12CVE-2023-35372same vendor as the line abovesame change as the line aboveDays to revision 217
2024-03-12CVE-2023-36866same vendor as the line abovesame change as the line aboveDays to revision 217
Fri 26 Jan 2024· 1 record change
2024-01-26CVE-2024-21337not named as affected at publication, now names microsoft edge (chromium-based) extended stableDays to revision 14
Fri 12 Jan 2024· 4 record changes
2024-01-12CVE-2024-0057not named as affected at publication, now names powershell 7.2 and 2 moreDays to revision 3
2024-01-12CVE-2024-0057same vendor as the line abovenot named as affected at publication, now names powershell 7.2Days to revision 3
2024-01-12CVE-2024-0057same vendor as the line abovenot named as affected at publication, now names powershell 7.3Days to revision 3
2024-01-12CVE-2024-0057same vendor as the line abovenot named as affected at publication, now names powershell 7.4Days to revision 3
2024-01-12CVE-2024-21307not named as affected at publication, now names remote desktop client for windows desktopDays to revision 3
Tue 9 Jan 2024· 31 record changes
2024-01-092 commits31 rows, one per record and productnot named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10) and 5 moreBranches and original-value intervals are stated on each row.Days to revision 56 to 208
2024-01-09CVE-2023-29349same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10)Days to revision 208
2024-01-09CVE-2023-29349same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2022 version 17.2Days to revision 208
2024-01-09CVE-2023-29349same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2022 version 17.4Days to revision 208
2024-01-09CVE-2023-29349same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2022 version 17.6Days to revision 208
2024-01-09CVE-2023-29349same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2022 version 17.8Days to revision 208
2024-01-09CVE-2023-29356same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10)Days to revision 208
2024-01-09CVE-2023-29356same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2022 version 17.2Days to revision 208
2024-01-09CVE-2023-29356same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2022 version 17.4Days to revision 208
23 more rows in this change are not listed here. Open all 31 rows
Mon 6 Nov 2023· 29 record changes
2023-11-064 commits29 rows, one per record and productnot named as affected at publication, now names powershell 7.3 and 10 moreBranches and original-value intervals are stated on each row.Days to revision 27 to 90
2023-11-06CVE-2023-36435same vendor as the line abovenot named as affected at publication, now names powershell 7.3Days to revision 27
2023-11-06CVE-2023-38171same vendor as the line abovenot named as affected at publication, now names powershell 7.3Days to revision 27
2023-11-06CVE-2023-36788same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.6.2Days to revision 55
2023-11-06CVE-2023-36788same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.6.2/4.7/4.7.1/4.7.2Days to revision 55
2023-11-06CVE-2023-36792same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.6.2Days to revision 55
2023-11-06CVE-2023-36792same vendor as the line abovenot named as affected at publication, now names microsoft .net framework 3.5 and 4.6.2/4.7/4.7.1/4.7.2Days to revision 55
2023-11-06CVE-2023-36792same vendor as the line abovenot named as affected at publication, now names microsoft visual studio 2022 version 17.6Days to revision 55
2023-11-06CVE-2023-36792same vendor as the line abovenot named as affected at publication, now names powershell 7.2Days to revision 55
21 more rows in this change are not listed here. Open all 29 rows
Tue 1 Aug 2023· 2 record changes
2023-08-01CVE-2023-28260not named as affected at publication, now names powershell 7.2 and 1 moreDays to revision 112
2023-08-01CVE-2023-28260same vendor as the line abovenot named as affected at publication, now names powershell 7.2Days to revision 112
2023-08-01CVE-2023-28260same vendor as the line abovenot named as affected at publication, now names powershell 7.3Days to revision 112
Fri 21 Jul 2023· 1 record change
2023-07-21CVE-2023-21538not named as affected at publication, now names powershell 7.2Days to revision 193
Fri 14 Jul 2023· 3 record changes
2023-07-14CVE-2023-32052not named as affected at publication, now names microsoft power appsDays to revision 3
2023-07-14CVE-2023-33127not named as affected at publication, now names powershell 7.2 and 1 moreDays to revision 3
2023-07-14CVE-2023-33127same vendor as the line abovenot named as affected at publication, now names powershell 7.2Days to revision 3
2023-07-14CVE-2023-33127same vendor as the line abovenot named as affected at publication, now names powershell 7.3Days to revision 3
Fri 30 Jun 2023· 10 record changes
2023-06-302 commitsnot named as affected at publication, now names powershell 7.2Branches and original-value intervals are stated on each row.Days to revision 16 to 17
2023-06-30CVE-2023-24895same vendor as the line abovesame change as the line aboveDays to revision 16
2023-06-30CVE-2023-24936same vendor as the line abovesame change as the line aboveDays to revision 16
2023-06-30CVE-2023-29331same vendor as the line abovesame change as the line aboveDays to revision 16
2023-06-30CVE-2023-33126same vendor as the line abovesame change as the line aboveDays to revision 17
2023-06-30CVE-2023-24897same vendor as the line abovesame change as the line aboveDays to revision 16
2023-06-30not named as affected at publication, now names powershell 7.3Days to revision 16 to 17
2023-06-30CVE-2023-24895same vendor as the line abovesame change as the line aboveDays to revision 16
2023-06-30CVE-2023-24936same vendor as the line abovesame change as the line aboveDays to revision 16
2023-06-30CVE-2023-29331same vendor as the line abovesame change as the line aboveDays to revision 16
2023-06-30CVE-2023-32032same vendor as the line abovesame change as the line aboveDays to revision 17
2023-06-30CVE-2023-33128same vendor as the line abovesame change as the line aboveDays to revision 17
Fri 28 Apr 2023· 1 record change
2023-04-28CVE-2023-24934not named as affected at publication, now names microsoft malware protection platformDays to revision 14

This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller. 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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

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 →