Every change, newest first
| 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. |
|---|---|---|---|---|---|
| Tue 8 Jul 2025· 1 change | |||||
| 2025-07-08 | CVSS base score changed | CVE-2025-49691 | whole record microsoft | stated at publication 8.8, now states 8.0CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| Mon 16 Jun 2025· 1 change | |||||
| 2025-06-16 | Product added | CVE-2024-38179 | not named as affected at publication, now names azure stack os hci | Time to revision 250 days | |
| Thu 12 Jun 2025· 1 change | |||||
| 2025-06-12 | CVSS base score changed | CVE-2025-47977 | whole record microsoft | stated at publication 7.6, now states 8.2CVSS v3.1 · base scoreHighHigh | Time to revision 2 days |
| Thu 22 May 2025· 1 change | |||||
| 2025-05-22 | Fix version moved | CVE-2025-26646 | microsoftmicrosoft visual studio 2022 version 17.10 | stated at publication 17.10.14, now states 17.10.15Release branch starts at 17.10. | Time to revision 9 days |
| Thu 15 May 2025· 21 changes | |||||
| 2025-05-152 commits | Product added | 20 rows, one per record and product | not 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. | Time to revision 2 days | |
| 2025-05-15 | same kind of change as the line above | CVE-2025-29977 | same vendor as the line above | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Time to revision 2 days |
| 2025-05-15 | same kind of change as the line above | CVE-2025-29977 | same vendor as the line above | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Time to revision 2 days |
| 2025-05-15 | same kind of change as the line above | CVE-2025-29979 | same vendor as the line above | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Time to revision 2 days |
| 2025-05-15 | same kind of change as the line above | CVE-2025-29979 | same vendor as the line above | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Time to revision 2 days |
| 2025-05-15 | same kind of change as the line above | CVE-2025-30375 | same vendor as the line above | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Time to revision 2 days |
| 2025-05-15 | same kind of change as the line above | CVE-2025-30375 | same vendor as the line above | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Time to revision 2 days |
| 2025-05-15 | same kind of change as the line above | CVE-2025-30379 | same vendor as the line above | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Time to revision 2 days |
| 2025-05-15 | same kind of change as the line above | CVE-2025-30379 | same vendor as the line above | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Time to revision 2 days |
| 12 more rows in this change are not listed here. Open all 20 rows → | |||||
| 2025-05-15 | CVSS base score changed | CVE-2025-29833 | whole record microsoft | stated at publication 7.1, now states 7.7CVSS v3.1 · base scoreHighHigh | Time to revision 2 days |
| Fri 11 Apr 2025· 1 change | |||||
| 2025-04-11 | CVSS base score changed | CVE-2025-26647 | whole record microsoft | stated at publication 8.1, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 3 days |
| Thu 3 Apr 2025· 1 change | |||||
| 2025-04-03 | CVSS base score changed | CVE-2025-24071 | whole record microsoft | stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 23 days |
| Tue 11 Mar 2025· 4 changes | |||||
| 2025-03-11 | Fix version moved | CVE-2025-24036 | microsoftmicrosoft autoupdate for mac | stated at publication 4.77.24121924, now states 4.78.25022527Release branch starts at 0. | Time to revision 28 days |
| 2025-03-11 | Product added | CVE-2024-30098 | not named as affected at publication, now names windows 11 version 24h2 and 2 more | Time to revision 245 days | |
| 2025-03-11 | same kind of change as the line above | CVE-2024-30098 | same vendor as the line above | not named as affected at publication, now names windows 11 version 24h2 | Time to revision 245 days |
| 2025-03-11 | same kind of change as the line above | CVE-2024-30098 | same vendor as the line above | not named as affected at publication, now names windows server 2025 | Time to revision 245 days |
| 2025-03-11 | same kind of change as the line above | CVE-2024-30098 | same vendor as the line above | not named as affected at publication, now names windows server 2025 (server core installation) | Time to revision 245 days |
| Fri 14 Feb 2025· 1 change | |||||
| 2025-02-14 | Product added | CVE-2025-21178 | not named as affected at publication, now names microsoft visual studio 2015 update 3 | Time to revision 31 days | |
| Tue 11 Feb 2025· 6 changes | |||||
| 2025-02-11 | Fix version moved | CVE-2025-21198 | microsoftmicrosoft hpc pack 2019 | stated at publication 6.3.8322.0, now states 6.3.8328.0Release branch starts at 1.0.0.same day | Time to revision 0 days |
| 2025-02-11 | Product added | CVE-2023-24932 | not named as affected at publication, now names windows 11 version 24h2 and 2 more | Time to revision 644 days | |
| 2025-02-11 | same kind of change as the line above | CVE-2023-24932 | same vendor as the line above | not named as affected at publication, now names windows 11 version 24h2 | Time to revision 644 days |
| 2025-02-11 | same kind of change as the line above | CVE-2023-24932 | same vendor as the line above | not named as affected at publication, now names windows server 2025 | Time to revision 644 days |
| 2025-02-11 | same kind of change as the line above | CVE-2023-24932 | same vendor as the line above | not named as affected at publication, now names windows server 2025 (server core installation) | Time to revision 644 days |
| 2025-02-112 commits | Product added | not named as affected at publication, now names microsoft visual studio 2015 update 3Branches and original-value intervals are stated on each row. | Time to revision 28 days | ||
| 2025-02-11 | same kind of change as the line above | CVE-2025-21172 | same vendor as the line above | same change as the line above | Time to revision 28 days |
| 2025-02-11 | same kind of change as the line above | CVE-2025-21176 | same vendor as the line above | same change as the line above | Time to revision 28 days |
| Thu 6 Feb 2025· 1 change | |||||
| 2025-02-06 | CVSS base score changed | CVE-2025-21396 | whole record microsoft | stated at publication 7.5, now states 8.2CVSS v3.1 · base scoreHighHigh | Time to revision 8 days |
| Wed 29 Jan 2025· 4 changes | |||||
| 2025-01-293 commits | Product added | not named as affected at publication, now names powershell 7.5Branches and original-value intervals are stated on each row. | Time to revision 15 to 113 days | ||
| 2025-01-29 | same kind of change as the line above | CVE-2024-43485 | same vendor as the line above | same change as the line above | Time to revision 113 days |
| 2025-01-29 | same kind of change as the line above | CVE-2024-43498 | same vendor as the line above | same change as the line above | Time to revision 78 days |
| 2025-01-29 | same kind of change as the line above | CVE-2024-43499 | same vendor as the line above | same change as the line above | Time to revision 78 days |
| 2025-01-29 | same kind of change as the line above | CVE-2025-21171 | same vendor as the line above | same change as the line above | Time to revision 15 days |
| Tue 14 Jan 2025· 2 changes | |||||
| 2025-01-14 | CVSS base score changed | whole record microsoft | stated at publication 7.8, now states 8.4CVSS v3.1 · base scoreHighHigh | Time to revision 0 days | |
| 2025-01-14 | same kind of change as the line above | CVE-2025-21354 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-01-14 | same kind of change as the line above | CVE-2025-21362 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| Tue 31 Dec 2024· 5 changes | |||||
| 2024-12-31 | Fix version moved | CVE-2024-29059 | microsoftmicrosoft .net framework 3.5 and 4.8 | stated at publication 4.8.4682.0, now states 4.8.04690.02Release branch starts at 4.8.0.Original value first replaced 2024-05-08; this value first seen 2024-12-31. | Time to revision 47 days |
| 2024-12-31 | Fix version moved | CVE-2024-29059 | microsoftmicrosoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | stated at publication 4.7.4076.0, now states 4.7.04081.03Release branch starts at 4.7.0.Original value first replaced 2024-05-08; this value first seen 2024-12-31. | Time to revision 47 days |
| 2024-12-31 | Fix version moved | CVE-2024-49051 | microsoftmicrosoft pc manager | stated at publication 3.14.10.0, now states 3.14.14.0Release branch starts at 1.0.0. | Time to revision 49 days |
| 2024-12-31 | Product added | CVE-2024-35264 | not named as affected at publication, now names .net 6.0 | Time to revision 175 days | |
| 2024-12-31 | CVSS base score changed | CVE-2024-38183 | whole record microsoft | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 105 days |
| Fri 27 Dec 2024· 1 change | |||||
| 2024-12-27 | Product added | CVE-2024-30077 | not named as affected at publication, now names windows 11 version 24h2 | Time to revision 199 days | |
| Fri 20 Dec 2024· 3 changes | |||||
| 2024-12-20 | Product added | CVE-2024-43594 | not named as affected at publication, now names microsoft system center 2019 and 2 more | Time to revision 10 days | |
| 2024-12-20 | same kind of change as the line above | CVE-2024-43594 | same vendor as the line above | not named as affected at publication, now names microsoft system center 2019 | Time to revision 10 days |
| 2024-12-20 | same kind of change as the line above | CVE-2024-43594 | same vendor as the line above | not named as affected at publication, now names microsoft system center 2022 | Time to revision 10 days |
| 2024-12-20 | same kind of change as the line above | CVE-2024-43594 | same vendor as the line above | not named as affected at publication, now names microsoft system center 2025 | Time to revision 10 days |
| Tue 10 Dec 2024· 9 changes | |||||
| 2024-12-10 | Fix version moved | microsoft.net 7.0 | stated at publication 7.0.12, now states 7.0.13Release branch starts at 7.0.0. | Time to revision 427 days | |
| 2024-12-10 | same kind of change as the line above | CVE-2023-38171 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 427 days |
| 2024-12-10 | same kind of change as the line above | CVE-2023-36435 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 427 days |
| 2024-12-10 | Fix version moved | CVE-2023-38171 | microsoftmicrosoft visual studio 2022 version 17.2 | stated at publication 17.2.20, now states 17.2.21Release branch starts at 17.2.0. | Time to revision 427 days |
| 2024-12-10 | Fix version moved | CVE-2023-38171 | microsoftmicrosoft visual studio 2022 version 17.4 | stated at publication 17.4.12, now states 17.4.13Release branch starts at 17.4.0. | Time to revision 427 days |
| 2024-12-10 | Fix version moved | CVE-2023-38171 | microsoftmicrosoft visual studio 2022 version 17.6 | stated at publication 17.6.8, now states 17.6.9Release branch starts at 17.6.0. | Time to revision 427 days |
| 2024-12-10 | Fix version moved | CVE-2023-38171 | microsoftmicrosoft visual studio 2022 version 17.7 | stated at publication 17.7.5, now states 17.7.6Release branch starts at 17.7.0. | Time to revision 427 days |
| 2024-12-10 | Product added | CVE-2024-43583 | not named as affected at publication, now names windows server 2025 and 1 more | Time to revision 63 days | |
| 2024-12-10 | same kind of change as the line above | CVE-2024-43583 | same vendor as the line above | not named as affected at publication, now names windows server 2025 | Time to revision 63 days |
| 2024-12-10 | same kind of change as the line above | CVE-2024-43583 | same vendor as the line above | not named as affected at publication, now names windows server 2025 (server core installation) | Time to revision 63 days |
| 2024-12-10 | CVSS base score changed | CVE-2023-29348 | whole record microsoft | stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 427 days |
| Wed 27 Nov 2024· 3 changes | |||||
| 2024-11-27 | Fix version moved | CVE-2024-49040 | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.043, now states 15.01.2507.044Release branch starts at 15.01.0. | Time to revision 15 days |
| 2024-11-27 | Fix version moved | CVE-2024-49040 | microsoftmicrosoft exchange server 2019 cumulative update 13 | stated at publication 15.02.1258.038, now states 15.02.1258.039Release branch starts at 15.02.0. | Time to revision 15 days |
| 2024-11-27 | Fix version moved | CVE-2024-49040 | microsoftmicrosoft exchange server 2019 cumulative update 14 | stated at publication 15.02.1544.013, now states 15.02.1544.014Release branch starts at 15.02.0. | Time to revision 15 days |
| Thu 14 Nov 2024· 1 change | |||||
| 2024-11-14 | CVSS base score changed | CVE-2024-43598 | whole record microsoft | stated at publication 7.5, now states 8.1CVSS v3.1 · base scoreHighHigh | Time to revision 2 days |
| Fri 8 Nov 2024· 1 change | |||||
| 2024-11-08 | CVSS base score changed | CVE-2024-43601 | whole record microsoft | stated at publication 7.1, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 31 days |
| Wed 23 Oct 2024· 6 changes | |||||
| 2024-10-23 | Product added | 6 rows, one per record and product | not named as affected at publication, now names powershell 7.2 and 1 more | Time to revision 15 days | |
| 2024-10-23 | same kind of change as the line above | CVE-2024-43483 | same vendor as the line above | not named as affected at publication, now names powershell 7.2 | Time to revision 15 days |
| 2024-10-23 | same kind of change as the line above | CVE-2024-43483 | same vendor as the line above | not named as affected at publication, now names powershell 7.4 | Time to revision 15 days |
| 2024-10-23 | same kind of change as the line above | CVE-2024-43484 | same vendor as the line above | not named as affected at publication, now names powershell 7.2 | Time to revision 15 days |
| 2024-10-23 | same kind of change as the line above | CVE-2024-43484 | same vendor as the line above | not named as affected at publication, now names powershell 7.4 | Time to revision 15 days |
| 2024-10-23 | same kind of change as the line above | CVE-2024-43485 | same vendor as the line above | not named as affected at publication, now names powershell 7.2 | Time to revision 15 days |
| 2024-10-23 | same kind of change as the line above | CVE-2024-43485 | same vendor as the line above | not named as affected at publication, now names powershell 7.4 | Time to revision 15 days |
| Tue 8 Oct 2024· 4 changes | |||||
| 2024-10-08 | Fix version moved | CVE-2024-37341 | microsoftmicrosoft sql server 2016 service pack 3 azure connect feature pack | stated at publication 13.0.7040.1, now states 13.0.7045.2Release branch starts at 13.0.0. | Time to revision 28 days |
| 2024-10-08 | Fix version moved | CVE-2024-37341 | microsoftmicrosoft sql server 2022 (gdr) | stated at publication 16.0.1125.1, now states 16.0.1130.5Release branch starts at 16.0.0. | Time to revision 28 days |
| 2024-10-08 | Product added | CVE-2024-37341 | not named as affected at publication, now names microsoft sql server 2022 for (cu 15) | Time to revision 28 days | |
| 2024-10-08 | Product added | CVE-2024-38095 | not named as affected at publication, now names .net 6.0 | Time to revision 91 days | |
| Thu 19 Sep 2024· 2 changes | |||||
| 2024-09-19 | Fix version moved | microsoftazure stack hub | stated at publication 1.2311.1.22., now states 1.2406.1.15Release branch starts at 1.0.0. | Time to revision 9 days | |
| 2024-09-19 | same kind of change as the line above | CVE-2024-38216 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0. | Time to revision 9 days |
| 2024-09-19 | same kind of change as the line above | CVE-2024-38220 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0. | Time to revision 9 days |
| Tue 10 Sep 2024· 16 changes | |||||
| 2024-09-10 | Fix version moved | CVE-2024-38063 | microsoftwindows 11 version 21h2 | stated at publication 10.0.22000.3147, now states 10.0.22000.3197Release branch starts at 10.0.0. | Time to revision 28 days |
| 2024-09-10 | Product added | CVE-2024-38138 | not named as affected at publication, now names windows server 2008 service pack 2 and 8 more | Time to revision 28 days | |
| 2024-09-10 | same kind of change as the line above | CVE-2024-38138 | same vendor as the line above | not named as affected at publication, now names windows server 2008 service pack 2 | Time to revision 28 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-38138 | same vendor as the line above | not named as affected at publication, now names windows server 2008 r2 service pack 1 | Time to revision 28 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-38138 | same vendor as the line above | not named as affected at publication, now names windows server 2008 r2 service pack 1 (server core installation) | Time to revision 28 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-38138 | same vendor as the line above | not named as affected at publication, now names windows server 2008 service pack 2 | Time to revision 28 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-38138 | same vendor as the line above | not named as affected at publication, now names windows server 2008 service pack 2 (server core installation) | Time to revision 28 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-38138 | same vendor as the line above | not named as affected at publication, now names windows server 2012 | Time to revision 28 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-38138 | same vendor as the line above | not named as affected at publication, now names windows server 2012 (server core installation) | Time to revision 28 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-38138 | same vendor as the line above | not named as affected at publication, now names windows server 2012 r2 | Time to revision 28 days |
| 1 more row in this change is not listed here. Open all 9 rows → | |||||
| 2024-09-10 | Product added | CVE-2024-35272 | not named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8) and 5 more | Time to revision 63 days | |
| 2024-09-10 | same kind of change as the line above | CVE-2024-35272 | 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 63 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-35272 | 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 63 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-35272 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2022 version 17.10 | Time to revision 63 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-35272 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2022 version 17.11 | Time to revision 63 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-35272 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2022 version 17.6 | Time to revision 63 days |
| 2024-09-10 | same kind of change as the line above | CVE-2024-35272 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2022 version 17.8 | Time to revision 63 days |
| Tue 13 Aug 2024· 1 change | |||||
| 2024-08-13 | CVSS base score changed | CVE-2024-38200 | whole record microsoft | stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 5 days |
| Wed 31 Jul 2024· 1 change | |||||
| 2024-07-31 | CVSS base score changed | CVE-2024-37973 | whole record microsoft | stated at publication 8.4, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 22 days |
| Thu 25 Jul 2024· 4 changes | |||||
| 2024-07-25 | Product added | not named as affected at publication, now names powershell 7.4 | Time to revision 16 days | ||
| 2024-07-25 | same kind of change as the line above | CVE-2024-30105 | same vendor as the line above | same change as the line above | Time to revision 16 days |
| 2024-07-25 | same kind of change as the line above | CVE-2024-38095 | same vendor as the line above | same change as the line above | Time to revision 16 days |
| 2024-07-25 | Product added | CVE-2024-38081 | not named as affected at publication, now names .net 6.0 | Time to revision 16 days | |
| 2024-07-25 | Product added | CVE-2024-38095 | not named as affected at publication, now names powershell 7.2 | Time to revision 16 days | |
| Fri 19 Jul 2024· 2 changes | |||||
| 2024-07-19 | CVSS base score changed | CVE-2024-20652 | whole record microsoft | stated at publication 7.5, now states 8.1CVSS v3.1 · base scoreHighHigh | Time to revision 192 days |
| 2024-07-19 | CVSS base score changed | CVE-2024-21377 | whole record microsoft | stated at publication 7.1, now states 5.5CVSS v3.1 · base scoreHighMedium | Time to revision 157 days |
| Tue 9 Jul 2024· 1 change | |||||
| 2024-07-09 | Fix version moved | CVE-2023-24932 | microsoftwindows 10 version 1809 | stated at publication 10.0.17763.4377, now states 10.0.17763.6054Release branch starts at 10.0.0.Original value first replaced 2023-07-11; this value first seen 2024-07-09. | Time to revision 63 days |
| Wed 19 Jun 2024· 1 change | |||||
| 2024-06-19 | Product added | CVE-2024-30045 | not named as affected at publication, now names powershell 7.4 | Time to revision 36 days | |
| Thu 13 Jun 2024· 2 changes | |||||
| 2024-06-13 | Fix version moved | CVE-2024-35255 | microsoftazure identity library for c++ | stated at publication 1.7.0, now states 1.8.0Release branch starts at 1.0.0. | Time to revision 2 days |
| 2024-06-13 | CVSS base score changed | CVE-2024-30037 | whole record microsoft | stated at publication 7.5, now states 5.5CVSS v3.1 · base scoreHighMedium | Time to revision 30 days |
| Wed 29 May 2024· 1 change | |||||
| 2024-05-29 | CVSS base score changed | CVE-2023-35297 | whole record microsoft | stated at publication 7.5, now states 8.1CVSS v3.1 · base scoreHighHigh | Time to revision 322 days |
| Wed 15 May 2024· 4 changes | |||||
| 2024-05-15 | Fix version moved | CVE-2024-30041 | microsoftmicrosoft bing search for ios | stated at publication 28.2.000000000, now states 28.2.420417001Release branch starts at 1.0. | Time to revision 1 days |
| 2024-05-15 | Product added | CVE-2024-30046 | not named as affected at publication, now names .net 7.0 and 1 more | Time to revision 1 days | |
| 2024-05-15 | same kind of change as the line above | CVE-2024-30046 | same vendor as the line above | not named as affected at publication, now names .net 7.0 | Time to revision 1 days |
| 2024-05-15 | same kind of change as the line above | CVE-2024-30046 | same vendor as the line above | not named as affected at publication, now names .net 8.0 | Time to revision 1 days |
| 2024-05-15 | CVSS base score changed | CVE-2024-30044 | whole record microsoft | stated at publication 8.8, now states 7.2CVSS v3.1 · base scoreHighHigh | Time to revision 1 days |
| Tue 14 May 2024· 5 changes | |||||
| 2024-05-14 | Fix version moved | microsoftwindows 10 version 1809 | stated at publication 10.0.17763.5696, now states 10.0.17763.5820Release branch starts at 10.0.0. | Time to revision 35 days | |
| 2024-05-14 | same kind of change as the line above | CVE-2024-28902 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 35 days |
| 2024-05-14 | same kind of change as the line above | CVE-2024-26207 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 35 days |
| 2024-05-14 | same kind of change as the line above | CVE-2024-26211 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 35 days |
| 2024-05-14 | same kind of change as the line above | CVE-2024-26217 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 35 days |
| 2024-05-14 | same kind of change as the line above | CVE-2024-28900 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 35 days |
| Wed 8 May 2024· 4 changes | |||||
| 2024-05-08 | Fix version moved | CVE-2024-29059 | microsoft2 products | stated at publication 3.0.50727.8975, now states 3.0.50727.89762 release branches. Branches and original-value intervals are stated on each row. | Time to revision 47 days |
| 2024-05-08 | same kind of change as the line above | CVE-2024-29059 | same vendor as the line above | same change as the line aboveRelease branch starts at 2.0.0. | Time to revision 47 days |
| 2024-05-08 | same kind of change as the line above | CVE-2024-29059 | same vendor as the line above | same change as the line aboveRelease branch starts at 3.0.0. | Time to revision 47 days |
| 2024-05-08 | Fix version moved | CVE-2024-29059 | microsoftmicrosoft .net framework 3.5 and 4.8.1 | stated at publication 4.8.9206.0, now states 4.8.09214.01Release branch starts at 4.8.1. | Time to revision 47 days |
| 2024-05-08 | Fix version moved | CVE-2024-29059 | microsoftmicrosoft .net framework 4.6.2 | stated at publication 4.7.4076.0, now states 4.7.04081.03Release branch starts at 4.7.0. | Time to revision 47 days |
| Tue 23 Apr 2024· 2 changes | |||||
| 2024-04-23 | Fix version moved | CVE-2024-26198 | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.037, now states 15.01.2507.039Release branch starts at 15.01.0. | Time to revision 42 days |
| 2024-04-23 | Fix version moved | CVE-2024-26198 | microsoftmicrosoft exchange server 2019 cumulative update 13 | stated at publication 15.02.1258.032, now states 15.02.1544.011Release branch starts at 15.02.0. | Time to revision 42 days |
| Tue 16 Apr 2024· 7 changes | |||||
| 2024-04-16 | Product added | CVE-2024-21409 | not named as affected at publication, now names powershell 7.2 | Time to revision 7 days | |
| 2024-04-162 commits | Product added | not named as affected at publication, now names powershell 7.3Branches and original-value intervals are stated on each row. | Time to revision 7 to 35 days | ||
| 2024-04-16 | same kind of change as the line above | CVE-2024-21409 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2024-04-16 | same kind of change as the line above | CVE-2024-21392 | same vendor as the line above | same change as the line above | Time to revision 35 days |
| 2024-04-16 | same kind of change as the line above | CVE-2024-26190 | same vendor as the line above | same change as the line above | Time to revision 35 days |
| 2024-04-162 commits | Product added | not named as affected at publication, now names powershell 7.4Branches and original-value intervals are stated on each row. | Time to revision 7 to 35 days | ||
| 2024-04-16 | same kind of change as the line above | CVE-2024-21409 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2024-04-16 | same kind of change as the line above | CVE-2024-21392 | same vendor as the line above | same change as the line above | Time to revision 35 days |
| 2024-04-16 | same kind of change as the line above | CVE-2024-26190 | same vendor as the line above | same change as the line above | Time to revision 35 days |
| Thu 11 Apr 2024· 2 changes | |||||
| 2024-04-11 | Product added | CVE-2024-21330 | not named as affected at publication, now names azure hdinsight | Time to revision 30 days | |
| 2024-04-11 | CVSS base score changed | CVE-2024-21378 | whole record microsoft | stated at publication 8.0, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 58 days |
| Tue 9 Apr 2024· 3 changes | |||||
| 2024-04-09 | Product added | CVE-2023-24932 | not named as affected at publication, now names windows 11 version 22h3 and 2 more | Time to revision 336 days | |
| 2024-04-09 | same kind of change as the line above | CVE-2023-24932 | same vendor as the line above | not named as affected at publication, now names windows 11 version 22h3 | Time to revision 336 days |
| 2024-04-09 | same kind of change as the line above | CVE-2023-24932 | same vendor as the line above | not named as affected at publication, now names windows 11 version 23h2 | Time to revision 336 days |
| 2024-04-09 | same kind of change as the line above | CVE-2023-24932 | same vendor as the line above | not named as affected at publication, now names windows server 2022, 23h2 edition (server core installation) | Time to revision 336 days |
| Fri 22 Mar 2024· 7 changes | |||||
| 2024-03-22 | Fix version moved | CVE-2024-21388 | microsoftmicrosoft edge (chromium-based) | stated at publication 121.0.2277.83, now states 121.0.2277.98Release branch starts at 1.0.0. | Time to revision 52 days |
| 2024-03-22 | Product added | CVE-2024-0057 | not named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10) and 4 more | Time to revision 73 days | |
| 2024-03-22 | same kind of change as the line above | CVE-2024-0057 | 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 73 days |
| 2024-03-22 | same kind of change as the line above | CVE-2024-0057 | same vendor as the line above | not named as affected at publication, now names nuget 17.4.0 | Time to revision 73 days |
| 2024-03-22 | same kind of change as the line above | CVE-2024-0057 | same vendor as the line above | not named as affected at publication, now names nuget 17.6.0 | Time to revision 73 days |
| 2024-03-22 | same kind of change as the line above | CVE-2024-0057 | same vendor as the line above | not named as affected at publication, now names nuget 17.8.0 | Time to revision 73 days |
| 2024-03-22 | same kind of change as the line above | CVE-2024-0057 | same vendor as the line above | not named as affected at publication, now names nuget 5.11.0 | Time to revision 73 days |
| 2024-03-22 | Product added | CVE-2024-20677 | not named as affected at publication, now names 3d viewer | Time to revision 73 days | |
| Fri 15 Mar 2024· 1 change | |||||
| 2024-03-15 | Product added | CVE-2024-26163 | not named as affected at publication, now names microsoft edge (chromium-based) extended stable | Time to revision 1 days | |
| Tue 12 Mar 2024· 2 changes | |||||
| 2024-03-12 | Product added | not named as affected at publication, now names microsoft visio 2016 | Time to revision 217 days | ||
| 2024-03-12 | same kind of change as the line above | CVE-2023-35372 | same vendor as the line above | same change as the line above | Time to revision 217 days |
| 2024-03-12 | same kind of change as the line above | CVE-2023-36866 | same vendor as the line above | same change as the line above | Time to revision 217 days |
| Wed 14 Feb 2024· 1 change | |||||
| 2024-02-14 | CVSS base score changed | CVE-2024-21357 | whole record microsoft | stated at publication 7.5, now states 8.1CVSS v3.1 · base scoreHighHigh | Time to revision 1 days |
| Fri 26 Jan 2024· 1 change | |||||
| 2024-01-26 | Product added | CVE-2024-21337 | not named as affected at publication, now names microsoft edge (chromium-based) extended stable | Time to revision 14 days | |
| Fri 12 Jan 2024· 5 changes | |||||
| 2024-01-12 | Product added | CVE-2024-0057 | not named as affected at publication, now names powershell 7.2 and 2 more | Time to revision 3 days | |
| 2024-01-12 | same kind of change as the line above | CVE-2024-0057 | same vendor as the line above | not named as affected at publication, now names powershell 7.2 | Time to revision 3 days |
| 2024-01-12 | same kind of change as the line above | CVE-2024-0057 | same vendor as the line above | not named as affected at publication, now names powershell 7.3 | Time to revision 3 days |
| 2024-01-12 | same kind of change as the line above | CVE-2024-0057 | same vendor as the line above | not named as affected at publication, now names powershell 7.4 | Time to revision 3 days |
| 2024-01-12 | Product added | CVE-2024-21307 | not named as affected at publication, now names remote desktop client for windows desktop | Time to revision 3 days | |
| 2024-01-12 | CVSS base score changed | CVE-2024-20674 | whole record microsoft | stated at publication 9.0, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 3 days |
| Tue 9 Jan 2024· 32 changes | |||||
| 2024-01-092 commits | Product added | 31 rows, one per record and product | not 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. | Time to revision 56 to 208 days | |
| 2024-01-09 | same kind of change as the line above | CVE-2023-29349 | 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 208 days |
| 2024-01-09 | same kind of change as the line above | CVE-2023-29349 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2022 version 17.2 | Time to revision 208 days |
| 2024-01-09 | same kind of change as the line above | CVE-2023-29349 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2022 version 17.4 | Time to revision 208 days |
| 2024-01-09 | same kind of change as the line above | CVE-2023-29349 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2022 version 17.6 | Time to revision 208 days |
| 2024-01-09 | same kind of change as the line above | CVE-2023-29349 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2022 version 17.8 | Time to revision 208 days |
| 2024-01-09 | same kind of change as the line above | CVE-2023-29356 | 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 208 days |
| 2024-01-09 | same kind of change as the line above | CVE-2023-29356 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2022 version 17.2 | Time to revision 208 days |
| 2024-01-09 | same kind of change as the line above | CVE-2023-29356 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2022 version 17.4 | Time to revision 208 days |
| 23 more rows in this change are not listed here. Open all 31 rows → | |||||
| 2024-01-09 | CVSS base score changed | CVE-2023-36719 | whole record microsoft | stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 56 days |
| Thu 30 Nov 2023· 1 change | |||||
| 2023-11-30 | Fix version moved | CVE-2023-36796 | microsoftmicrosoft visual studio 2022 version 17.7 | stated at publication 17.7.4, now states 17.7.6Release branch starts at 17.7.0.Original value first replaced 2023-11-06; this value first seen 2023-11-30. | Time to revision 55 days |
| Thu 16 Nov 2023· 1 change | |||||
| 2023-11-16 | CVSS base score changed | CVE-2023-36423 | whole record microsoft | stated at publication 7.2, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 2 days |
| Thu 9 Nov 2023· 1 change | |||||
| 2023-11-09 | CVSS base score changed | CVE-2023-36034 | whole record microsoft | stated at publication 6.6, now states 7.3CVSS v3.1 · base scoreMediumHigh | Time to revision 7 days |
| Mon 6 Nov 2023· 60 changes | |||||
| 2023-11-06 | Fix version moved | microsoft.net 6.0 | stated at publication 6.0.22, now states 6.0.24Release branch starts at 6.0.0. | Time to revision 55 days | |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36799 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.0.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36796 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.0.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36794 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.0.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36793 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.0.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36792 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.0.0. | Time to revision 55 days |
| 2023-11-06 | Fix version moved | microsoft.net 7.0 | stated at publication 7.0.11, now states 7.0.13Release branch starts at 7.0.0. | Time to revision 55 days | |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36799 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36796 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36794 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36793 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36792 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 55 days |
| 2023-11-06 | Fix version moved | microsoftmicrosoft visual studio 2022 version 17.2 | stated at publication 17.2.19, now states 17.2.21Release branch starts at 17.2.0. | Time to revision 55 days | |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36799 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.2.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36796 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.2.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36794 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.2.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36793 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.2.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36792 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.2.0. | Time to revision 55 days |
| 2023-11-06 | Fix version moved | microsoftmicrosoft visual studio 2022 version 17.4 | stated at publication 17.4.11, now states 17.4.13Release branch starts at 17.4.0. | Time to revision 55 days | |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36799 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.4.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36796 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.4.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36794 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.4.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36793 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.4.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36792 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.4.0. | Time to revision 55 days |
| 2023-11-06 | Fix version moved | microsoftmicrosoft visual studio 2022 version 17.6 | stated at publication 17.6.7, now states 17.6.9Release branch starts at 17.6.0. | Time to revision 55 days | |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36799 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.6.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36796 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.6.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36794 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.6.0. | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36793 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.6.0. | Time to revision 55 days |
| 2023-11-064 commits | Product added | 29 rows, one per record and product | not named as affected at publication, now names powershell 7.3 and 10 moreBranches and original-value intervals are stated on each row. | Time to revision 27 to 90 days | |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36435 | same vendor as the line above | not named as affected at publication, now names powershell 7.3 | Time to revision 27 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-38171 | same vendor as the line above | not named as affected at publication, now names powershell 7.3 | Time to revision 27 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36788 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.6.2 | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36788 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36792 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.6.2 | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36792 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36792 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2022 version 17.6 | Time to revision 55 days |
| 2023-11-06 | same kind of change as the line above | CVE-2023-36792 | same vendor as the line above | not named as affected at publication, now names powershell 7.2 | Time to revision 55 days |
| 21 more rows in this change are not listed here. Open all 29 rows → | |||||
| 2023-11-06 | CVSS base score changed | CVE-2023-36420 | whole record microsoft | stated at publication 7.3, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 27 days |
| 2023-11-06 | CVSS base score changed | CVE-2023-36596 | whole record microsoft | stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 27 days |
| 2023-11-06 | CVSS base score changed | CVE-2023-36698 | whole record microsoft | stated at publication 3.6, now states 4.4CVSS v3.1 · base scoreLowMedium | Time to revision 27 days |
| 2023-11-06 | CVSS base score changed | CVE-2023-36761 | whole record microsoft | stated at publication 6.2, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 55 days |
| 2023-11-06 | CVSS base score changed | CVE-2023-35391 | whole record microsoft | stated at publication 7.1, now states 6.2CVSS v3.1 · base scoreHighMedium | Time to revision 90 days |
| 2023-11-06 | CVSS base score changed | CVE-2023-36899 | whole record microsoft | stated at publication 7.5, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 90 days |
| 2023-11-06 | CVSS base score changed | CVE-2023-36908 | whole record microsoft | stated at publication 5.7, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 90 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.
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 →