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. |
|---|---|---|---|---|---|
| Wed 12 Nov 2025· 7 record changes | |||||
| 2025-11-12 | Added to CISA KEV | CVE-2025-62215 | MicrosoftWindows CISA KEV | fix due 2025-12-03 | Not applicable: Added to CISA KEV has no earlier value |
| 2025-11-12 | Product added | 6 rows, one per record and product | not named as affected at publication, now names microsoft office ltsc for mac 2021 and 1 more | Days to revision 0 | |
| 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 | Days to revision 0 |
| 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 | Days to revision 0 |
| 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 | Days to revision 0 |
| 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 | Days to revision 0 |
| 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 | Days to revision 0 |
| 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 | Days to revision 0 |
| Fri 24 Oct 2025· 1 record change | |||||
| 2025-10-24 | Added to CISA KEV | CVE-2025-59287 | MicrosoftWindows CISA KEV | fix due 2025-11-14 | Not applicable: Added to CISA KEV has no earlier value |
| Mon 20 Oct 2025· 1 record change | |||||
| 2025-10-20 | Added to CISA KEV | CVE-2025-33073 | MicrosoftWindows CISA KEV | fix due 2025-11-10 | Not applicable: Added to CISA KEV has no earlier value |
| Wed 15 Oct 2025· 2 record 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. | Days to revision 1 |
| 2025-10-15 | Product added | CVE-2025-50173 | not named as affected at publication, now names multimedia redirection installer | Days to revision 64 | |
| Tue 14 Oct 2025· 2 record changes | |||||
| 2025-10-14 | Added to CISA KEV | MicrosoftWindows | fix due 2025-11-04 | Not applicable: Added to CISA KEV has no earlier value | |
| 2025-10-14 | same kind of change as the line above | CVE-2025-24990 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-10-14 | same kind of change as the line above | CVE-2025-59230 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| Wed 8 Oct 2025· 1 record change | |||||
| 2025-10-08 | Ransomware use confirmed | CVE-2024-21412 | MicrosoftWindows CISA KEV | stated at publication Unknown, now states Known | Days to revision at least 225 |
| Mon 6 Oct 2025· 4 record changes | |||||
| 2025-10-06 | Added to CISA KEV | CVE-2010-3962 | MicrosoftInternet Explorer CISA KEV | fix due 2025-10-27 | Not applicable: Added to CISA KEV has no earlier value |
| 2025-10-06 | Added to CISA KEV | MicrosoftWindows | fix due 2025-10-27 | Not applicable: Added to CISA KEV has no earlier value | |
| 2025-10-06 | same kind of change as the line above | CVE-2021-43226 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-10-06 | same kind of change as the line above | CVE-2013-3918 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-10-06 | same kind of change as the line above | CVE-2011-3402 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| Thu 11 Sep 2025· 2 record changes | |||||
| 2025-09-11 | Product added | CVE-2025-49734 | not named as affected at publication, now names powershell 7.4 and 1 more | Days to revision 2 | |
| 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 | Days to revision 2 |
| 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 | Days to revision 2 |
| Tue 9 Sep 2025· 16 record changes | |||||
| 2025-09-09 | Fix version moved | 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. | Days to revision 238 |
| 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. | Days to revision 238 |
| 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. | Days to revision 238 |
| 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. | Days to revision 238 |
| 2025-09-09 | Fix version moved | 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 2025-09-09 | Fix version moved | 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 2025-09-09 | Fix version moved | 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| Fri 15 Aug 2025· 6 record changes | |||||
| 2025-08-15 | Product added | CVE-2025-50171 | not named as affected at publication, now names windows 10 version 21h2 and 5 more | Days to revision 3 | |
| 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 | Days to revision 3 |
| 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 | Days to revision 3 |
| 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 | Days to revision 3 |
| 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 | Days to revision 3 |
| 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 | Days to revision 3 |
| 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 | Days to revision 3 |
| Tue 12 Aug 2025· 3 record changes | |||||
| 2025-08-12 | Added to CISA KEV | CVE-2007-0671 | MicrosoftOffice CISA KEV | fix due 2025-09-02 | Not applicable: Added to CISA KEV has no earlier value |
| 2025-08-12 | Added to CISA KEV | CVE-2013-3893 | MicrosoftInternet Explorer CISA KEV | fix due 2025-09-02 | Not applicable: Added to CISA KEV has no earlier value |
| 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 | Days to revision 0 |
| Tue 5 Aug 2025· 4 record changes | |||||
| 2025-08-05 | Ransomware use confirmed | CVE-2025-53770 | MicrosoftSharePoint CISA KEV | stated at publication Unknown, now states Known | Days to revision 15 |
| 2025-08-05 | KEV required action changed | MicrosoftSharePoint | stated at publication CISA recommends disconnecting public-facing versions of SharePoint Server that have reached their end-of-life (EOL) or end-of-service (EOS). For example, SharePoint Server 2013 and earlier versions are end-of-life and should be discontinued if still in use. For supported versions, please follow the mitigations according to CISA and vendor instructions. Adhere to the applicable BOD 22-01 guidance for cloud services or discontinue use of the product if mitigations are not available., now states Disconnect public-facing versions of SharePoint Server that have reached their end-of-life (EOL) or end-of-service (EOS) to include SharePoint Server 2013 and earlier versions. For supported versions, please follow the mitigations according to CISA (URL listed below in Notes) and vendor instructions (URL listed below in Notes). Adhere to the applicable BOD 22-01 guidance for cloud services or discontinue use of the product if mitigations are not available. | Days to revision 14 | |
| 2025-08-05 | same kind of change as the line above | CVE-2025-49704 | same vendor as the line above | same change as the line above | Days to revision 14 |
| 2025-08-05 | same kind of change as the line above | CVE-2025-49706 | same vendor as the line above | same change as the line above | Days to revision 14 |
| 2025-08-05 | KEV required action changed | CVE-2025-53770 | MicrosoftSharePoint CISA KEV | stated at publication CISA recommends configuring AMSI integration in SharePoint and deploying Defender AV on all SharePoint servers. If AMSI cannot be enabled, CISA recommends disconnecting affected products that are public-facing on the internet from service until official mitigations are available. Once mitigations are provided, apply them according to CISA and vendor instructions. Follow the applicable BOD 22-01 guidance for cloud services or discontinue use of the product if mitigations are not available. , now states Disconnect public-facing versions of SharePoint Server that have reached their end-of-life (EOL) or end-of-service (EOS) to include SharePoint Server 2013 and earlier versions. For supported versions, please follow the mitigations according to CISA (URL listed below in Notes) and vendor instructions (URL listed below in Notes). Adhere to the applicable BOD 22-01 guidance for cloud services or discontinue use of the product if mitigations are not available. | Days to revision 15 |
| Fri 25 Jul 2025· 2 record changes | |||||
| 2025-07-25 | Ransomware use confirmed | MicrosoftSharePoint | stated at publication Unknown, now states Known | Days to revision 3 | |
| 2025-07-25 | same kind of change as the line above | CVE-2025-49704 | same vendor as the line above | same change as the line above | Days to revision 3 |
| 2025-07-25 | same kind of change as the line above | CVE-2025-49706 | same vendor as the line above | same change as the line above | Days to revision 3 |
| Tue 22 Jul 2025· 2 record changes | |||||
| 2025-07-22 | Added to CISA KEV | MicrosoftSharePoint | fix due 2025-07-23 | Not applicable: Added to CISA KEV has no earlier value | |
| 2025-07-22 | same kind of change as the line above | CVE-2025-49704 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 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 above | Not applicable: Added to CISA KEV has no earlier value |
| Mon 21 Jul 2025· 1 record change | |||||
| 2025-07-21 | Added to CISA KEV | CVE-2025-53770 | MicrosoftSharePoint CISA KEV | fix due 2025-07-21 · listed 2025-07-20 | Not applicable: Added to CISA KEV has no earlier value |
| Fri 18 Jul 2025· 1 record change | |||||
| 2025-07-18 | Ransomware use confirmed | CVE-2019-0708 | MicrosoftRemote Desktop Services CISA KEV | stated at publication Unknown, now states Known | Days to revision at least 143 |
| Fri 11 Jul 2025· 1 record change | |||||
| 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. | Days to revision 31 |
| Tue 8 Jul 2025· 4 record 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. | Days to revision 238 |
| 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. | Days to revision 238 |
| 2025-07-08 | Product added | CVE-2025-30399 | not named as affected at publication, now names powershell 7.4 and 1 more | Days to revision 26 | |
| 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 | Days to revision 26 |
| 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 | Days to revision 26 |
| Mon 16 Jun 2025· 1 record change | |||||
| 2025-06-16 | Product added | CVE-2024-38179 | not named as affected at publication, now names azure stack os hci | Days to revision 250 | |
| Thu 22 May 2025· 1 record 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. | Days to revision 9 |
| Thu 15 May 2025· 20 record 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. | Days to revision 2 | |
| 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 | Days to revision 2 |
| 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 | Days to revision 2 |
| 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 | Days to revision 2 |
| 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 | Days to revision 2 |
| 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 | Days to revision 2 |
| 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 | Days to revision 2 |
| 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 | Days to revision 2 |
| 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 | Days to revision 2 |
| 12 more rows in this change are not listed here. Open all 20 rows → | |||||
| Tue 13 May 2025· 7 record changes | |||||
| 2025-05-13 | Added to CISA KEV | MicrosoftWindows | fix due 2025-06-03 | Not applicable: Added to CISA KEV has no earlier value | |
| 2025-05-13 | same kind of change as the line above | CVE-2025-32709 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-05-13 | same kind of change as the line above | CVE-2025-30397 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-05-13 | same kind of change as the line above | CVE-2025-32706 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-05-13 | same kind of change as the line above | CVE-2025-32701 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-05-13 | same kind of change as the line above | CVE-2025-30400 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-05-13 | Ransomware use confirmed | MicrosoftWindows | stated at publication Unknown, now states Known | not dated | |
| 2025-05-13 | same kind of change as the line above | CVE-2022-21999 | same vendor as the line above | same change as the line above | Days to revision at least 77 |
| 2025-05-13 | same kind of change as the line above | CVE-2021-43890 | same vendor as the line above | same change as the line above | Days to revision at least 77 |
| Mon 12 May 2025· 3 record changes | |||||
| 2025-05-12 | Ransomware use confirmed | MicrosoftWindows | stated at publication Unknown, now states Known | not dated | |
| 2025-05-12 | same kind of change as the line above | CVE-2022-41091 | same vendor as the line above | same change as the line above | Days to revision at least 76 |
| 2025-05-12 | same kind of change as the line above | CVE-2022-30190 | same vendor as the line above | same change as the line above | Days to revision at least 76 |
| 2025-05-12 | same kind of change as the line above | CVE-2014-1812 | same vendor as the line above | same change as the line above | Days to revision at least 76 |
| Thu 17 Apr 2025· 1 record change | |||||
| 2025-04-17 | Added to CISA KEV | CVE-2025-24054 | MicrosoftWindows CISA KEV | fix due 2025-05-08 | Not applicable: Added to CISA KEV has no earlier value |
| Wed 9 Apr 2025· 1 record change | |||||
| 2025-04-09 | Ransomware use confirmed | CVE-2025-29824 | MicrosoftWindows CISA KEV | stated at publication Unknown, now states Known | Days to revision 1 |
| Tue 8 Apr 2025· 1 record change | |||||
| 2025-04-08 | Added to CISA KEV | CVE-2025-29824 | MicrosoftWindows CISA KEV | fix due 2025-04-29 | Not applicable: Added to CISA KEV has no earlier value |
| Mon 7 Apr 2025· 3 record changes | |||||
| 2025-04-07 | Ransomware use confirmed | CVE-2018-8639 | MicrosoftWindows CISA KEV | stated at publication Unknown, now states Known | Days to revision 35 |
| 2025-04-07 | Ransomware use confirmed | CVE-2024-38094 | MicrosoftSharePoint CISA KEV | stated at publication Unknown, now states Known | Days to revision at least 41 |
| 2025-04-07 | Ransomware use confirmed | CVE-2024-30051 | MicrosoftDWM Core Library CISA KEV | stated at publication Unknown, now states Known | Days to revision at least 41 |
| Mon 31 Mar 2025· 1 record change | |||||
| 2025-03-31 | Ransomware use confirmed | CVE-2025-26633 | MicrosoftWindows CISA KEV | stated at publication Unknown, now states Known | Days to revision 20 |
| Tue 18 Mar 2025· 1 record change | |||||
| 2025-03-18 | Ransomware use confirmed | CVE-2023-23376 | MicrosoftWindows CISA KEV | stated at publication Unknown, now states Known | Days to revision at least 21 |
| Tue 11 Mar 2025· 10 record changes | |||||
| 2025-03-11 | Added to CISA KEV | MicrosoftWindows | fix due 2025-04-01 | Not applicable: Added to CISA KEV has no earlier value | |
| 2025-03-11 | same kind of change as the line above | CVE-2025-24993 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-03-11 | same kind of change as the line above | CVE-2025-24991 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-03-11 | same kind of change as the line above | CVE-2025-24985 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-03-11 | same kind of change as the line above | CVE-2025-24984 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-03-11 | same kind of change as the line above | CVE-2025-24983 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-03-11 | same kind of change as the line above | CVE-2025-26633 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 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. | Days to revision 28 |
| 2025-03-11 | Product added | CVE-2024-30098 | not named as affected at publication, now names windows 11 version 24h2 and 2 more | Days to revision 245 | |
| 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 | Days to revision 245 |
| 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 | Days to revision 245 |
| 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) | Days to revision 245 |
| Mon 3 Mar 2025· 1 record change | |||||
| 2025-03-03 | Added to CISA KEV | CVE-2018-8639 | MicrosoftWindows CISA KEV | fix due 2025-03-24 | Not applicable: Added to CISA KEV has no earlier value |
| Tue 25 Feb 2025· 1 record change | |||||
| 2025-02-25 | Added to CISA KEV | CVE-2024-49035 | MicrosoftPartner Center CISA KEV | fix due 2025-03-18 | Not applicable: Added to CISA KEV has no earlier value |
| Fri 21 Feb 2025· 1 record change | |||||
| 2025-02-21 | Added to CISA KEV | CVE-2025-24989 | MicrosoftPower Pages CISA KEV | fix due 2025-03-14 | Not applicable: Added to CISA KEV has no earlier value |
| Fri 14 Feb 2025· 1 record change | |||||
| 2025-02-14 | Product added | CVE-2025-21178 | not named as affected at publication, now names microsoft visual studio 2015 update 3 | Days to revision 31 | |
| Tue 11 Feb 2025· 8 record changes | |||||
| 2025-02-11 | Added to CISA KEV | MicrosoftWindows | fix due 2025-03-04 | Not applicable: Added to CISA KEV has no earlier value | |
| 2025-02-11 | same kind of change as the line above | CVE-2025-21418 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 2025-02-11 | same kind of change as the line above | CVE-2025-21391 | same vendor as the line above | same change as the line above | Not applicable: Added to CISA KEV has no earlier value |
| 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 | Days to revision 0 |
| 2025-02-11 | Product added | CVE-2023-24932 | not named as affected at publication, now names windows 11 version 24h2 and 2 more | Days to revision 644 | |
| 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 | Days to revision 644 |
| 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 | Days to revision 644 |
| 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) | Days to revision 644 |
| 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. | Days to revision 28 | ||
| 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 | Days to revision 28 |
| 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 | Days to revision 28 |
| Fri 7 Feb 2025· 1 record change | |||||
| 2025-02-07 | Added to CISA KEV | CVE-2024-21413 | MicrosoftOffice Outlook CISA KEV | fix due 2025-02-27 · listed 2025-02-06 | Not applicable: Added to CISA KEV has no earlier value |
| Tue 4 Feb 2025· 1 record change | |||||
| 2025-02-04 | Added to CISA KEV | CVE-2024-29059 | Microsoft.NET Framework CISA KEV | fix due 2025-02-25 | Not applicable: Added to CISA KEV has no earlier value |
| Wed 29 Jan 2025· 4 record 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. | Days to revision 15 to 113 | ||
| 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 | Days to revision 113 |
| 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 | Days to revision 78 |
| 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 | Days to revision 78 |
| 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 | Days to revision 15 |
| Tue 31 Dec 2024· 4 record 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. | Days to revision 47 |
| 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. | Days to revision 47 |
| 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. | Days to revision 49 |
| 2024-12-31 | Product added | CVE-2024-35264 | not named as affected at publication, now names .net 6.0 | Days to revision 175 | |
| Fri 27 Dec 2024· 1 record change | |||||
| 2024-12-27 | Product added | CVE-2024-30077 | not named as affected at publication, now names windows 11 version 24h2 | Days to revision 199 | |
| Fri 20 Dec 2024· 3 record changes | |||||
| 2024-12-20 | Product added | CVE-2024-43594 | not named as affected at publication, now names microsoft system center 2019 and 2 more | Days to revision 10 | |
| 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 | Days to revision 10 |
| 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 | Days to revision 10 |
| 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 | Days to revision 10 |
| Tue 10 Dec 2024· 8 record 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. | Days to revision 427 | |
| 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. | Days to revision 427 |
| 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. | Days to revision 427 |
| 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. | Days to revision 427 |
| 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. | Days to revision 427 |
| 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. | Days to revision 427 |
| 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. | Days to revision 427 |
| 2024-12-10 | Product added | CVE-2024-43583 | not named as affected at publication, now names windows server 2025 and 1 more | Days to revision 63 | |
| 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 | Days to revision 63 |
| 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) | Days to revision 63 |
| Wed 27 Nov 2024· 3 record 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. | Days to revision 15 |
| 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. | Days to revision 15 |
| 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. | Days to revision 15 |
| Wed 23 Oct 2024· 6 record 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 | Days to revision 15 | |
| 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 | Days to revision 15 |
| 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 | Days to revision 15 |
| 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 | Days to revision 15 |
| 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 | Days to revision 15 |
| 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 | Days to revision 15 |
| 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 | Days to revision 15 |
| Tue 8 Oct 2024· 4 record 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. | Days to revision 28 |
| 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. | Days to revision 28 |
| 2024-10-08 | Product added | CVE-2024-37341 | not named as affected at publication, now names microsoft sql server 2022 for (cu 15) | Days to revision 28 | |
| 2024-10-08 | Product added | CVE-2024-38095 | not named as affected at publication, now names .net 6.0 | Days to revision 91 | |
| Thu 19 Sep 2024· 2 record 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. | Days to revision 9 | |
| 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. | Days to revision 9 |
| 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. | Days to revision 9 |
| Tue 10 Sep 2024· 16 record 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. | Days to revision 28 |
| 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 | Days to revision 28 | |
| 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 | Days to revision 28 |
| 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 | Days to revision 28 |
| 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) | Days to revision 28 |
| 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 | Days to revision 28 |
| 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) | Days to revision 28 |
| 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 | Days to revision 28 |
| 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) | Days to revision 28 |
| 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 | Days to revision 28 |
| 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 | Days to revision 63 | |
| 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) | Days to revision 63 |
| 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) | Days to revision 63 |
| 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 | Days to revision 63 |
| 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 | Days to revision 63 |
| 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 | Days to revision 63 |
| 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 | Days to revision 63 |
| Thu 25 Jul 2024· 4 record changes | |||||
| 2024-07-25 | Product added | not named as affected at publication, now names powershell 7.4 | Days to revision 16 | ||
| 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 | Days to revision 16 |
| 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 | Days to revision 16 |
| 2024-07-25 | Product added | CVE-2024-38081 | not named as affected at publication, now names .net 6.0 | Days to revision 16 | |
| 2024-07-25 | Product added | CVE-2024-38095 | not named as affected at publication, now names powershell 7.2 | Days to revision 16 | |
| Tue 9 Jul 2024· 1 record 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. | Days to revision 63 |
| Wed 19 Jun 2024· 1 record change | |||||
| 2024-06-19 | Product added | CVE-2024-30045 | not named as affected at publication, now names powershell 7.4 | Days to revision 36 | |
| Thu 13 Jun 2024· 1 record change | |||||
| 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. | Days to revision 2 |
| Wed 15 May 2024· 3 record 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. | Days to revision 1 |
| 2024-05-15 | Product added | CVE-2024-30046 | not named as affected at publication, now names .net 7.0 and 1 more | Days to revision 1 | |
| 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 | Days to revision 1 |
| 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 | Days to revision 1 |
| Tue 14 May 2024· 5 record 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. | Days to revision 35 | |
| 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. | Days to revision 35 |
| 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. | Days to revision 35 |
| 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. | Days to revision 35 |
| 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. | Days to revision 35 |
| 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. | Days to revision 35 |
| Wed 8 May 2024· 4 record 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. | Days to revision 47 |
| 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. | Days to revision 47 |
| 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. | Days to revision 47 |
| 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. | Days to revision 47 |
| 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. | Days to revision 47 |
| Tue 23 Apr 2024· 2 record 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. | Days to revision 42 |
| 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. | Days to revision 42 |
Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. 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.
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 →