Every change, newest first

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

690 changes · newest first · grouped by dayCSV JSON RSS

Counted changes from microsoft, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.	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 changes
2025-11-12	Added to CISA KEV	CVE-2025-62215	MicrosoftWindows CISA KEV	fix due 2025-12-03	Duration unknown
2025-11-12	Product added	Show all 3 CVE records in this change: Product added: 2 products named as affected from microsoftHide the 3 CVE records in this change: Product added: 2 products named as affected from microsoft6 rows, one per record and product	microsoft	not named as affected at publication, now names microsoft office ltsc for mac 2021 and 1 more	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-60726	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2021	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-60726	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2024	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-60727	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2021	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-60727	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2024	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-62203	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2021	Time to revision 0 days
2025-11-12	same kind of change as the line above	CVE-2025-62203	same vendor as the line above	not named as affected at publication, now names microsoft office ltsc for mac 2024	Time to revision 0 days
Fri 24 Oct 2025· 1 change
2025-10-24	Added to CISA KEV	CVE-2025-59287	MicrosoftWindows CISA KEV	fix due 2025-11-14	Duration unknown
Mon 20 Oct 2025· 1 change
2025-10-20	Added to CISA KEV	CVE-2025-33073	MicrosoftWindows CISA KEV	fix due 2025-11-10	Duration unknown
Wed 15 Oct 2025· 2 changes
2025-10-15	Fix version moved	CVE-2025-58724	microsoftarc enabled servers - azure connected machine agent	stated at publication 1.56, now states 1.57Release branch starts at 1.0.0.	Time to revision 1 days
2025-10-15	Product added	CVE-2025-50173	microsoft	not named as affected at publication, now names multimedia redirection installer	Time to revision 64 days
Tue 14 Oct 2025· 2 changes
2025-10-14	Added to CISA KEV	Show all 2 CVE records in this change: Added to CISA KEV: Windows from MicrosoftHide the 2 CVE records in this change: Added to CISA KEV: Windows from Microsoft	MicrosoftWindows	fix due 2025-11-04	Duration unknown
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	Duration unknown
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	Duration unknown
Wed 8 Oct 2025· 1 change
2025-10-08	Ransomware use confirmed	CVE-2024-21412	MicrosoftWindows CISA KEV	stated at publication Unknown, now states Known	Duration unknown
Mon 6 Oct 2025· 4 changes
2025-10-06	Added to CISA KEV	CVE-2010-3962	MicrosoftInternet Explorer CISA KEV	fix due 2025-10-27	Duration unknown
2025-10-06	Added to CISA KEV	Show all 3 CVE records in this change: Added to CISA KEV: Windows from MicrosoftHide the 3 CVE records in this change: Added to CISA KEV: Windows from Microsoft	MicrosoftWindows	fix due 2025-10-27	Duration unknown
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	Duration unknown
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	Duration unknown
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	Duration unknown
Thu 11 Sep 2025· 2 changes
2025-09-11	Product added	CVE-2025-49734Show all 2 products in this change: Product added: 2 products named as affected in CVE-2025-49734Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2025-49734	microsoft	not named as affected at publication, now names powershell 7.4 and 1 more	Time to revision 2 days
2025-09-11	same kind of change as the line above	CVE-2025-49734	same vendor as the line above	not named as affected at publication, now names powershell 7.4	Time to revision 2 days
2025-09-11	same kind of change as the line above	CVE-2025-49734	same vendor as the line above	not named as affected at publication, now names powershell 7.5	Time to revision 2 days
Tue 9 Sep 2025· 16 changes
2025-09-09	Fix version moved	CVE-2025-21293Show all 3 products in this change: Fix version moved: 10.0.26100.2894 → 10.0.26100.6584 in CVE-2025-21293Hide the 3 products in this change: Fix version moved: 10.0.26100.2894 → 10.0.26100.6584 in CVE-2025-21293	microsoft3 products	stated at publication 10.0.26100.2894, now states 10.0.26100.6584Release branch starts at 10.0.26100.0.	Time to revision 238 days
2025-09-09	same kind of change as the line above	CVE-2025-21293	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 238 days
2025-09-09	same kind of change as the line above	CVE-2025-21293	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 238 days
2025-09-09	same kind of change as the line above	CVE-2025-21293	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 238 days
2025-09-09	Fix version moved	CVE-2025-48807Show all 3 products in this change: Fix version moved: 10.0.14393.8246 → 10.0.14393.8422 in CVE-2025-48807Hide the 3 products in this change: Fix version moved: 10.0.14393.8246 → 10.0.14393.8422 in CVE-2025-48807	microsoft3 products	stated at publication 10.0.14393.8246, now states 10.0.14393.8422Release branch starts at 10.0.14393.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.14393.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.14393.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.14393.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807Show all 3 products in this change: Fix version moved: 10.0.17763.7558 → 10.0.17763.7792 in CVE-2025-48807Hide the 3 products in this change: Fix version moved: 10.0.17763.7558 → 10.0.17763.7792 in CVE-2025-48807	microsoft3 products	stated at publication 10.0.17763.7558, now states 10.0.17763.7792Release branch starts at 10.0.17763.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.17763.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.17763.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.17763.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807	microsoftwindows 10 version 21h2	stated at publication 10.0.19044.6093, now states 10.0.19044.6332Release branch starts at 10.0.19044.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807	microsoftwindows 11 version 22h2	stated at publication 10.0.22621.5624, now states 10.0.22621.5909Release branch starts at 10.0.22621.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807Show all 3 products in this change: Fix version moved: 10.0.26100.4652 → 10.0.26100.6584 in CVE-2025-48807Hide the 3 products in this change: Fix version moved: 10.0.26100.4652 → 10.0.26100.6584 in CVE-2025-48807	microsoft3 products	stated at publication 10.0.26100.4652, now states 10.0.26100.6584Release branch starts at 10.0.26100.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 28 days
2025-09-09	same kind of change as the line above	CVE-2025-48807	same vendor as the line above	same change as the line aboveRelease branch starts at 10.0.26100.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807	microsoftwindows server 2022	stated at publication 10.0.20348.3932, now states 10.0.20348.4171Release branch starts at 10.0.20348.0.	Time to revision 28 days
2025-09-09	Fix version moved	CVE-2025-48807	microsoftwindows server 2022, 23h2 edition (server core installation)	stated at publication 10.0.25398.1732, now states 10.0.25398.1849Release branch starts at 10.0.25398.0.	Time to revision 28 days
Fri 15 Aug 2025· 6 changes
2025-08-15	Product added	CVE-2025-50171Show all 6 products in this change: Product added: 6 products named as affected in CVE-2025-50171Hide the 6 products in this change: Product added: 6 products named as affected in CVE-2025-50171	microsoft	not named as affected at publication, now names windows 10 version 21h2 and 5 more	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 10 version 21h2	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 10 version 22h2	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 11 version 22h2	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 11 version 22h3	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 11 version 23h2	Time to revision 3 days
2025-08-15	same kind of change as the line above	CVE-2025-50171	same vendor as the line above	not named as affected at publication, now names windows 11 version 24h2	Time to revision 3 days
Tue 12 Aug 2025· 3 changes
2025-08-12	Added to CISA KEV	CVE-2007-0671	MicrosoftOffice CISA KEV	fix due 2025-09-02	Duration unknown
2025-08-12	Added to CISA KEV	CVE-2013-3893	MicrosoftInternet Explorer CISA KEV	fix due 2025-09-02	Duration unknown
2025-08-12	Fix version moved	CVE-2025-53729	microsoftazure file sync	stated at publication 18.0.0.0, now states 18.3.0.0Release branch starts at 1.0.0.same day	Time to revision 0 days
Tue 5 Aug 2025· 4 changes
2025-08-05	Ransomware use confirmed	CVE-2025-53770	MicrosoftSharePoint CISA KEV	stated at publication Unknown, now states Known	Time to revision 15 days
2025-08-05	KEV required action changed	Show all 2 CVE records in this change: KEV required action changed: 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. → 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. from MicrosoftHide the 2 CVE records in this change: KEV required action changed: 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. → 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. from Microsoft	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.	Time to revision 14 days
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	Time to revision 14 days
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	Time to revision 14 days
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.	Time to revision 15 days
Fri 25 Jul 2025· 2 changes
2025-07-25	Ransomware use confirmed	Show all 2 CVE records in this change: Ransomware use confirmed: Unknown → Known from MicrosoftHide the 2 CVE records in this change: Ransomware use confirmed: Unknown → Known from Microsoft	MicrosoftSharePoint	stated at publication Unknown, now states Known	Time to revision 3 days
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	Time to revision 3 days
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	Time to revision 3 days
Tue 22 Jul 2025· 2 changes
2025-07-22	Added to CISA KEV	Show all 2 CVE records in this change: Added to CISA KEV: SharePoint from MicrosoftHide the 2 CVE records in this change: Added to CISA KEV: SharePoint from Microsoft	MicrosoftSharePoint	fix due 2025-07-23	Duration unknown
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	Duration unknown
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	Duration unknown
Mon 21 Jul 2025· 1 change
2025-07-21	Added to CISA KEV	CVE-2025-53770	MicrosoftSharePoint CISA KEV	fix due 2025-07-21 · listed 2025-07-20	Duration unknown
Fri 18 Jul 2025· 1 change
2025-07-18	Ransomware use confirmed	CVE-2019-0708	MicrosoftRemote Desktop Services CISA KEV	stated at publication Unknown, now states Known	Duration unknown
Fri 11 Jul 2025· 1 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.	Time to revision 31 days
Tue 8 Jul 2025· 4 changes
2025-07-08	Fix version moved	CVE-2024-49000	microsoftmicrosoft sql server 2016 service pack 3 (gdr)	stated at publication 13.0.6455.2, now states 13.0.6460.7Release branch starts at 13.0.0.	Time to revision 238 days
2025-07-08	Fix version moved	CVE-2024-49000	microsoftmicrosoft sql server 2016 service pack 3 azure connect feature pack	stated at publication 13.0.7050.2, now states 13.0.7055.9Release branch starts at 13.0.0.	Time to revision 238 days
2025-07-08	Product added	CVE-2025-30399Show all 2 products in this change: Product added: 2 products named as affected in CVE-2025-30399Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2025-30399	microsoft	not named as affected at publication, now names powershell 7.4 and 1 more	Time to revision 26 days
2025-07-08	same kind of change as the line above	CVE-2025-30399	same vendor as the line above	not named as affected at publication, now names powershell 7.4	Time to revision 26 days
2025-07-08	same kind of change as the line above	CVE-2025-30399	same vendor as the line above	not named as affected at publication, now names powershell 7.5	Time to revision 26 days
Mon 16 Jun 2025· 1 change
2025-06-16	Product added	CVE-2024-38179	microsoft	not named as affected at publication, now names azure stack os hci	Time to revision 250 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· 20 changes
2025-05-152 commits	Product added	Show all 9 CVE records in this change: Product added: 6 products named as affected from microsoftHide the 9 CVE records in this change: Product added: 6 products named as affected from microsoft20 rows, one per record and product	microsoft	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 →
Tue 13 May 2025· 7 changes
2025-05-13	Added to CISA KEV	Show all 5 CVE records in this change: Added to CISA KEV: Windows from MicrosoftHide the 5 CVE records in this change: Added to CISA KEV: Windows from Microsoft	MicrosoftWindows	fix due 2025-06-03	Duration unknown
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	Duration unknown
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	Duration unknown
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	Duration unknown
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	Duration unknown
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	Duration unknown
2025-05-13	Ransomware use confirmed	Show all 2 CVE records in this change: Ransomware use confirmed: Unknown → Known from MicrosoftHide the 2 CVE records in this change: Ransomware use confirmed: Unknown → Known from Microsoft	MicrosoftWindows	stated at publication Unknown, now states Known	Duration unknown
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	Duration unknown
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	Duration unknown
Mon 12 May 2025· 3 changes
2025-05-12	Ransomware use confirmed	Show all 3 CVE records in this change: Ransomware use confirmed: Unknown → Known from MicrosoftHide the 3 CVE records in this change: Ransomware use confirmed: Unknown → Known from Microsoft	MicrosoftWindows	stated at publication Unknown, now states Known	Duration unknown
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	Duration unknown
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	Duration unknown
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	Duration unknown
Thu 17 Apr 2025· 1 change
2025-04-17	Added to CISA KEV	CVE-2025-24054	MicrosoftWindows CISA KEV	fix due 2025-05-08	Duration unknown
Wed 9 Apr 2025· 1 change
2025-04-09	Ransomware use confirmed	CVE-2025-29824	MicrosoftWindows CISA KEV	stated at publication Unknown, now states Known	Time to revision 1 days
Tue 8 Apr 2025· 1 change
2025-04-08	Added to CISA KEV	CVE-2025-29824	MicrosoftWindows CISA KEV	fix due 2025-04-29	Duration unknown
Mon 7 Apr 2025· 3 changes
2025-04-07	Ransomware use confirmed	CVE-2018-8639	MicrosoftWindows CISA KEV	stated at publication Unknown, now states Known	Time to revision 35 days
2025-04-07	Ransomware use confirmed	CVE-2024-38094	MicrosoftSharePoint CISA KEV	stated at publication Unknown, now states Known	Duration unknown
2025-04-07	Ransomware use confirmed	CVE-2024-30051	MicrosoftDWM Core Library CISA KEV	stated at publication Unknown, now states Known	Duration unknown
Mon 31 Mar 2025· 1 change
2025-03-31	Ransomware use confirmed	CVE-2025-26633	MicrosoftWindows CISA KEV	stated at publication Unknown, now states Known	Time to revision 20 days
Tue 18 Mar 2025· 1 change
2025-03-18	Ransomware use confirmed	CVE-2023-23376	MicrosoftWindows CISA KEV	stated at publication Unknown, now states Known	Duration unknown
Tue 11 Mar 2025· 10 changes
2025-03-11	Added to CISA KEV	Show all 6 CVE records in this change: Added to CISA KEV: Windows from MicrosoftHide the 6 CVE records in this change: Added to CISA KEV: Windows from Microsoft	MicrosoftWindows	fix due 2025-04-01	Duration unknown
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	Duration unknown
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	Duration unknown
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	Duration unknown
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	Duration unknown
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	Duration unknown
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	Duration unknown
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-30098Show all 3 products in this change: Product added: 3 products named as affected in CVE-2024-30098Hide the 3 products in this change: Product added: 3 products named as affected in CVE-2024-30098	microsoft	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
Mon 3 Mar 2025· 1 change
2025-03-03	Added to CISA KEV	CVE-2018-8639	MicrosoftWindows CISA KEV	fix due 2025-03-24	Duration unknown
Tue 25 Feb 2025· 1 change
2025-02-25	Added to CISA KEV	CVE-2024-49035	MicrosoftPartner Center CISA KEV	fix due 2025-03-18	Duration unknown
Fri 21 Feb 2025· 1 change
2025-02-21	Added to CISA KEV	CVE-2025-24989	MicrosoftPower Pages CISA KEV	fix due 2025-03-14	Duration unknown
Fri 14 Feb 2025· 1 change
2025-02-14	Product added	CVE-2025-21178	microsoft	not named as affected at publication, now names microsoft visual studio 2015 update 3	Time to revision 31 days
Tue 11 Feb 2025· 8 changes
2025-02-11	Added to CISA KEV	Show all 2 CVE records in this change: Added to CISA KEV: Windows from MicrosoftHide the 2 CVE records in this change: Added to CISA KEV: Windows from Microsoft	MicrosoftWindows	fix due 2025-03-04	Duration unknown
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	Duration unknown
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	Duration unknown
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-24932Show all 3 products in this change: Product added: 3 products named as affected in CVE-2023-24932Hide the 3 products in this change: Product added: 3 products named as affected in CVE-2023-24932	microsoft	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	Show all 2 CVE records in this change: Product added: microsoft visual studio 2015 update 3 named as affected from microsoftHide the 2 CVE records in this change: Product added: microsoft visual studio 2015 update 3 named as affected from microsoft	microsoft	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
Fri 7 Feb 2025· 1 change
2025-02-07	Added to CISA KEV	CVE-2024-21413	MicrosoftOffice Outlook CISA KEV	fix due 2025-02-27 · listed 2025-02-06	Duration unknown
Tue 4 Feb 2025· 1 change
2025-02-04	Added to CISA KEV	CVE-2024-29059	Microsoft.NET Framework CISA KEV	fix due 2025-02-25	Duration unknown
Wed 29 Jan 2025· 4 changes
2025-01-293 commits	Product added	Show all 4 CVE records in this change: Product added: powershell 7.5 named as affected from microsoftHide the 4 CVE records in this change: Product added: powershell 7.5 named as affected from microsoft	microsoft	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 31 Dec 2024· 4 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	microsoft	not named as affected at publication, now names .net 6.0	Time to revision 175 days
Fri 27 Dec 2024· 1 change
2024-12-27	Product added	CVE-2024-30077	microsoft	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-43594Show all 3 products in this change: Product added: 3 products named as affected in CVE-2024-43594Hide the 3 products in this change: Product added: 3 products named as affected in CVE-2024-43594	microsoft	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· 8 changes
2024-12-10	Fix version moved	Show all 2 CVE records in this change: Fix version moved: 7.0.12 → 7.0.13 from microsoftHide the 2 CVE records in this change: Fix version moved: 7.0.12 → 7.0.13 from microsoft	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-43583Show all 2 products in this change: Product added: 2 products named as affected in CVE-2024-43583Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2024-43583	microsoft	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
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
Wed 23 Oct 2024· 6 changes
2024-10-23	Product added	Show all 3 CVE records in this change: Product added: 2 products named as affected from microsoftHide the 3 CVE records in this change: Product added: 2 products named as affected from microsoft6 rows, one per record and product	microsoft	not named as affected at publication, now names 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	microsoft	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	microsoft	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	Show all 2 CVE records in this change: Fix version moved: 1.2311.1.22. → 1.2406.1.15 from microsoftHide the 2 CVE records in this change: Fix version moved: 1.2311.1.22. → 1.2406.1.15 from microsoft	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-38138Show all 9 products in this change: Product added: 9 products named as affected in CVE-2024-38138Hide the 9 products in this change: Product added: 9 products named as affected in CVE-2024-38138	microsoft	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-35272Show all 6 products in this change: Product added: 6 products named as affected in CVE-2024-35272Hide the 6 products in this change: Product added: 6 products named as affected in CVE-2024-35272	microsoft	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
Thu 25 Jul 2024· 4 changes
2024-07-25	Product added	Show all 2 CVE records in this change: Product added: powershell 7.4 named as affected from microsoftHide the 2 CVE records in this change: Product added: powershell 7.4 named as affected from microsoft	microsoft	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	microsoft	not named as affected at publication, now names .net 6.0	Time to revision 16 days
2024-07-25	Product added	CVE-2024-38095	microsoft	not named as affected at publication, now names powershell 7.2	Time to revision 16 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	microsoft	not named as affected at publication, now names powershell 7.4	Time to revision 36 days
Thu 13 Jun 2024· 1 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.	Time to revision 2 days
Wed 15 May 2024· 3 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-30046Show all 2 products in this change: Product added: 2 products named as affected in CVE-2024-30046Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2024-30046	microsoft	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
Tue 14 May 2024· 5 changes
2024-05-14	Fix version moved	Show all 5 CVE records in this change: Fix version moved: 10.0.17763.5696 → 10.0.17763.5820 from microsoftHide the 5 CVE records in this change: Fix version moved: 10.0.17763.5696 → 10.0.17763.5820 from microsoft	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-29059Show all 2 products in this change: Fix version moved: 3.0.50727.8975 → 3.0.50727.8976 in CVE-2024-29059Hide the 2 products in this change: Fix version moved: 3.0.50727.8975 → 3.0.50727.8976 in 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

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.

Every kind of change

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

To a CVE record or a KEV entry

To a GitHub advisory

What this page cannot see

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.

The units, the refusals, the cut-offs and every source, in full →

Paste your closed CVE tickets and see which of these changes hit them →