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. |
|---|---|---|---|---|---|
| Fri 4 Sep 2026· 1 change | |||||
| 2026-09-04 | Ransomware use confirmed | CVE-2022-37969 | MicrosoftWindows CISA KEV | stated at publication Unknown, now states Known | Duration unknown |
| Thu 3 Sep 2026· 1 change | |||||
| 2026-09-03 | Product added | CVE-2026-58641 | not named as affected at publication, now names skiasharp | Time to revision 23 days | |
| Wed 2 Sep 2026· 9 changes | |||||
| 2026-09-02 | Fix version moved | CVE-2026-65675 | microsoftmicrosoft visual studio code copilot chat extension | stated at publication 1.132.1, now states 1.135Release branch starts at 0.27.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | Fix version moved | microsoftvisual studio code | stated at publication 1.132.1, now states 1.135Release branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days | |
| 2026-09-02 | same kind of change as the line above | CVE-2026-58650 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-59113 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-47285 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-69320 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-69278 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-69306 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-70335 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-70336 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| Fri 28 Aug 2026· 1 change | |||||
| 2026-08-28 | Product added | CVE-2026-59133 | not named as affected at publication, now names microsoft hpc pack 2019 | Time to revision 17 days | |
| Wed 26 Aug 2026· 1 change | |||||
| 2026-08-26 | Added to CISA KEV | CVE-2019-1068 | MicrosoftSQL Server CISA KEV | fix due 2026-08-29 | Duration unknown |
| Fri 21 Aug 2026· 3 changes | |||||
| 2026-08-21 | Added to CISA KEV | CVE-2026-69836 | MicrosoftEntra ID CISA KEV | fix due 2026-08-24 | Duration unknown |
| 2026-08-21 | Ransomware use confirmed | CVE-2021-43226 | MicrosoftWindows CISA KEV | stated at publication Unknown, now states Known | Time to revision 319 days |
| 2026-08-21 | Ransomware use confirmed | CVE-2012-0158 | MicrosoftMSCOMCTL.OCX CISA KEV | stated at publication Unknown, now states Known | Duration unknown |
| Tue 18 Aug 2026· 2 changes | |||||
| 2026-08-18 | Added to CISA KEV | CVE-2026-33824 | MicrosoftInternet Key Exchange (IKE) Service Extensions CISA KEV | fix due 2026-08-21 | Duration unknown |
| 2026-08-18 | Added to CISA KEV | CVE-2026-55040 | MicrosoftSharePoint CISA KEV | fix due 2026-08-21 | Duration unknown |
| Sun 16 Aug 2026· 1 change | |||||
| 2026-08-16 | Product added | CVE-2026-59124 | not named as affected at publication, now names microsoft hpc pack 2019 | Time to revision 5 days | |
| Fri 14 Aug 2026· 25 changes | |||||
| 2026-08-14 | Ransomware use confirmed | CVE-2025-60710 | MicrosoftWindows CISA KEV | stated at publication Unknown, now states Known | Time to revision 123 days |
| 2026-08-14 | Ransomware use confirmed | CVE-2020-0618 | MicrosoftSQL Server CISA KEV | stated at publication Unknown, now states Known | Duration unknown |
| 2026-08-14 | Ransomware use confirmed | MicrosoftInternet Explorer | stated at publication Unknown, now states Known | Duration unknown | |
| 2026-08-14 | same kind of change as the line above | CVE-2016-0189 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-08-14 | same kind of change as the line above | CVE-2020-0968 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-08-14 | Ransomware use confirmed | MicrosoftWin32k | stated at publication Unknown, now states Known | Duration unknown | |
| 2026-08-14 | same kind of change as the line above | CVE-2022-21882 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-08-14 | same kind of change as the line above | CVE-2019-0803 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-08-14 | Ransomware use confirmed | CVE-2018-0802 | MicrosoftOffice CISA KEV | stated at publication Unknown, now states Known | Duration unknown |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoft3 products | stated at publication 10.0.14393.9060, now states 10.0.14393.9339Release branch starts at 10.0.14393.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoft3 products | stated at publication 10.0.17763.8644, now states 10.0.17763.9020Release branch starts at 10.0.17763.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 10 version 21h2 | stated at publication 10.0.19044.7184, now states 10.0.19044.7548Release branch starts at 10.0.19044.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7184, now states 10.0.19045.7548Release branch starts at 10.0.19045.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 11 version 23h2 | stated at publication 10.0.22631.6936, now states 10.0.22631.7376Release branch starts at 10.0.22631.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 11 version 25h2 | stated at publication 10.0.26200.8246, now states 10.0.26200.8875Release branch starts at 10.0.26200.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.1836, now states 10.0.28000.2525Release branch starts at 10.0.28000.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoft2 products | stated at publication 6.2.9200.26026, now states 6.2.9200.26226Release branch starts at 6.2.9200.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoft2 products | stated at publication 6.3.9600.23132, now states 6.3.9600.23291Release branch starts at 6.3.9600.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2022 | stated at publication 10.0.20348.5020, now states 10.0.20348.5386Release branch starts at 10.0.20348.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoft2 products | stated at publication 10.0.26100.32690, now states 10.0.26100.33158Release branch starts at 10.0.26100.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0. | Time to revision 122 days |
| Thu 13 Aug 2026· 25 changes | |||||
| 2026-08-13 | Product added | not named as affected at publication, now names office online server | Time to revision 2 days | ||
| 2026-08-13 | same kind of change as the line above | CVE-2026-65807 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68793 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68794 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68795 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68796 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68797 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68799 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68800 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 17 more rows in this change are not listed here. Open all 25 rows → | |||||
| Tue 11 Aug 2026· 2 changes | |||||
| 2026-08-11 | Added to CISA KEV | CVE-2026-68820 | MicrosoftWindows Ancillary Function Driver for WinSock CISA KEV | fix due 2026-08-25 | Duration unknown |
| 2026-08-11 | Product added | CVE-2026-59118 | not named as affected at publication, now names copilot cowork | Time to revision 5 days | |
| Mon 10 Aug 2026· 1 change | |||||
| 2026-08-10 | Ransomware use confirmed | CVE-2026-45659 | MicrosoftSharePoint Server CISA KEV | stated at publication Unknown, now states Known | Time to revision 40 days |
| Tue 28 Jul 2026· 28 changes | |||||
| 2026-07-28 | Fix version moved | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.069, now states 15.01.2507.071Release branch starts at 15.01.0.0. | Time to revision 49 days | |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45500 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45501 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45502 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45503 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45504 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45583 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-47631 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | microsoftmicrosoft exchange server 2019 cumulative update 14 | stated at publication 15.02.1544.041, now states 15.02.1544.043Release branch starts at 15.02.0.0. | Time to revision 49 days | |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45500 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45501 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45502 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45503 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45504 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45583 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-47631 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | microsoftmicrosoft exchange server 2019 cumulative update 15 | stated at publication 15.02.1748.046, now states 15.02.1748.048Release branch starts at 15.02.0.0. | Time to revision 49 days | |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45500 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45501 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45502 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45503 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45504 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45583 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-47631 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | microsoftmicrosoft exchange server subscription edition rtm | stated at publication 15.02.2562.043, now states 15.02.2562.045Release branch starts at 15.02.0.0. | Time to revision 49 days | |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45500 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45501 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45502 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45503 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45504 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-45583 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | same kind of change as the line above | CVE-2026-47631 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.0. | Time to revision 49 days |
| Sun 26 Jul 2026· 2 changes | |||||
| 2026-07-26 | Product added | CVE-2026-48561 | not named as affected at publication, now names microsoft edge copilot for android and 1 more | Time to revision 12 days | |
| 2026-07-26 | same kind of change as the line above | CVE-2026-48561 | same vendor as the line above | not named as affected at publication, now names microsoft edge copilot for android | Time to revision 12 days |
| 2026-07-26 | same kind of change as the line above | CVE-2026-48561 | same vendor as the line above | not named as affected at publication, now names microsoft edge copilot for ios | Time to revision 12 days |
| Wed 22 Jul 2026· 27 changes | |||||
| 2026-07-22 | Added to CISA KEV | CVE-2026-50522 | MicrosoftSharePoint CISA KEV | fix due 2026-07-25 | Duration unknown |
| 2026-07-222 commits | Fix version moved | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Branches and original-value intervals are stated on each row. | Time to revision 8 days | |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50524 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50525 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50526 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50527 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50528 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50648 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50651 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50659 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0. | Time to revision 8 days |
| 3 more rows in this change are not listed here. Open all 11 rows → | |||||
| 2026-07-22 | Product added | CVE-2026-47304 | not named as affected at publication, now names .net 10.0 and 2 more | Time to revision 8 days | |
| 2026-07-22 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names .net 10.0 | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names .net 8.0 | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names .net 9.0 | Time to revision 8 days |
| 2026-07-22 | Product added | not named as affected at publication, now names microsoft .net framework 4.8.1 | Time to revision 8 days | ||
| 2026-07-22 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50304 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50324 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50355 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50368 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50411 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50525 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2026-07-22 | same kind of change as the line above | CVE-2026-50647 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 4 more rows in this change are not listed here. Open all 12 rows → | |||||
| Tue 21 Jul 2026· 3 changes | |||||
| 2026-07-21 | Product added | CVE-2026-47304 | not named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8) and 2 more | Time to revision 7 days | |
| 2026-07-21 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2017 version 15.9 (includes 15.0 - 15.8) | Time to revision 7 days |
| 2026-07-21 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2019 version 16.11 (includes 16.0 - 16.10) | Time to revision 7 days |
| 2026-07-21 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names microsoft visual studio 2026 version 18.5 | Time to revision 7 days |
| Thu 16 Jul 2026· 43 changes | |||||
| 2026-07-16 | Added to CISA KEV | CVE-2026-58644 | MicrosoftSharePoint CISA KEV | fix due 2026-07-19 | Duration unknown |
| 2026-07-16 | Product added | 42 rows, one per record and product | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 and 5 more | Time to revision 2 days | |
| 2026-07-16 | same kind of change as the line above | CVE-2026-50304 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 2 days |
| 2026-07-16 | same kind of change as the line above | CVE-2026-50304 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 2 days |
| 2026-07-16 | same kind of change as the line above | CVE-2026-50304 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 2 days |
| 2026-07-16 | same kind of change as the line above | CVE-2026-50304 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 2 days |
| 2026-07-16 | same kind of change as the line above | CVE-2026-50304 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 4.8 | Time to revision 2 days |
| 2026-07-16 | same kind of change as the line above | CVE-2026-50324 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 2 days |
| 2026-07-16 | same kind of change as the line above | CVE-2026-50324 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 2 days |
| 2026-07-16 | same kind of change as the line above | CVE-2026-50324 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 2 days |
| 34 more rows in this change are not listed here. Open all 42 rows → | |||||
| Wed 15 Jul 2026· 24 changes | |||||
| 2026-07-15 | Product added | 24 rows, one per record and product | not named as affected at publication, now names microsoft .net framework 3.5 and 5 more | Time to revision 1 days | |
| 2026-07-15 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 | Time to revision 1 days |
| 2026-07-15 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 1 days |
| 2026-07-15 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 1 days |
| 2026-07-15 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 1 days |
| 2026-07-15 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 1 days |
| 2026-07-15 | same kind of change as the line above | CVE-2026-47304 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 4.8 | Time to revision 1 days |
| 2026-07-15 | same kind of change as the line above | CVE-2026-50525 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 | Time to revision 1 days |
| 2026-07-15 | same kind of change as the line above | CVE-2026-50525 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 1 days |
| 16 more rows in this change are not listed here. Open all 24 rows → | |||||
| Tue 14 Jul 2026· 2 changes | |||||
| 2026-07-14 | Added to CISA KEV | CVE-2026-56155 | MicrosoftActive Directory Federation Services CISA KEV | fix due 2026-07-28 | Duration unknown |
| 2026-07-14 | Added to CISA KEV | CVE-2026-56164 | MicrosoftSharePoint Server CISA KEV | fix due 2026-07-17 | Duration unknown |
| Wed 1 Jul 2026· 1 change | |||||
| 2026-07-01 | Added to CISA KEV | CVE-2026-45659 | MicrosoftSharePoint Server CISA KEV | fix due 2026-07-04 | Duration unknown |
| Mon 29 Jun 2026· 1 change | |||||
| 2026-06-29 | Ransomware use confirmed | CVE-2026-33825 | MicrosoftDefender CISA KEV | stated at publication Unknown, now states Known | Time to revision 68 days |
| Mon 15 Jun 2026· 3 changes | |||||
| 2026-06-15 | Fix version moved | microsoftvisual studio code | stated at publication 1.123.1, now states 1.123.2Release branch starts at 1.0.0. | Time to revision 6 days | |
| 2026-06-15 | same kind of change as the line above | CVE-2026-47287 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0. | Time to revision 6 days |
| 2026-06-15 | same kind of change as the line above | CVE-2026-47281 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0. | Time to revision 6 days |
| 2026-06-15 | same kind of change as the line above | CVE-2026-47284 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0. | Time to revision 6 days |
| Wed 10 Jun 2026· 3 changes | |||||
| 2026-06-10 | Fix version moved | microsoftvisual studio code | stated at publication 1.119.1, now states 1.123.2Release branch starts at 1.0.0. | Time to revision 1 days | |
| 2026-06-10 | same kind of change as the line above | CVE-2026-40376 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0. | Time to revision 1 days |
| 2026-06-10 | same kind of change as the line above | CVE-2026-48569 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0. | Time to revision 1 days |
| 2026-06-10 | Fix version moved | CVE-2026-45482 | microsoftmicrosoft visual studio code copilot chat extension | stated at publication 1.123.1, now states 1.123.2Release branch starts at 0.27.0. | Time to revision 1 days |
| Tue 9 Jun 2026· 69 changes | |||||
| 2026-06-09 | Fix version moved | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7291, now states 10.0.19045.7417Release branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days | |
| 2026-06-09 | same kind of change as the line above | CVE-2026-21530 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-33834 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-33839 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-33841 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-34329 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-34330 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-34331 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-34333 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.19045.0.bulk ×54 | Time to revision 28 days |
| 45 more rows in this change are not listed here. Open all 53 rows → | |||||
| 2026-06-09 | Fix version moved | CVE-2026-32175 | microsoftmicrosoft visual studio 2022 version 17.14 | stated at publication 17.14.31, now states 17.14.32Release branch starts at 17.14.0.bulk ×54 | Time to revision 28 days |
| 2026-06-092 commits | Product added | 15 rows, one per record and product | not named as affected at publication, now names microsoft excel for android and 10 moreBranches and original-value intervals are stated on each row. | Time to revision 28 to 609 days | |
| 2026-06-09 | same kind of change as the line above | CVE-2026-41100 | same vendor as the line above | not named as affected at publication, now names microsoft excel for android | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-41100 | same vendor as the line above | not named as affected at publication, now names microsoft loop for android | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-41100 | same vendor as the line above | not named as affected at publication, now names microsoft onenote for android | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-41100 | same vendor as the line above | not named as affected at publication, now names microsoft powerpoint for android | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2026-41100 | same vendor as the line above | not named as affected at publication, now names microsoft word for android | Time to revision 28 days |
| 2026-06-09 | same kind of change as the line above | CVE-2024-43582 | same vendor as the line above | not named as affected at publication, now names windows 11 version 26h1 | Time to revision 609 days |
| 2026-06-09 | same kind of change as the line above | CVE-2024-49075 | same vendor as the line above | not named as affected at publication, now names windows 11 version 26h1 | Time to revision 546 days |
| 2026-06-09 | same kind of change as the line above | CVE-2024-49123 | same vendor as the line above | not named as affected at publication, now names windows 11 version 26h1 | Time to revision 546 days |
| 7 more rows in this change are not listed here. Open all 15 rows → | |||||
| Fri 5 Jun 2026· 1 change | |||||
| 2026-06-05 | Fix version moved | CVE-2026-32177 | microsoftmicrosoft visual studio 2022 version 17.14 | stated at publication 17.14.31, now states 17.14.32Release branch starts at 17.14.0. | Time to revision 24 days |
| Wed 20 May 2026· 6 changes | |||||
| 2026-05-20 | Added to CISA KEV | CVE-2010-0249 | MicrosoftInternet Explorer CISA KEV | fix due 2026-06-03 · listed 2026-06-03 | Duration unknown |
| 2026-05-20 | Added to CISA KEV | CVE-2008-4250 | MicrosoftWindows CISA KEV | fix due 2026-06-03 | Duration unknown |
| 2026-05-20 | Added to CISA KEV | CVE-2009-1537 | MicrosoftDirectX CISA KEV | fix due 2026-06-03 | Duration unknown |
| 2026-05-20 | Added to CISA KEV | CVE-2010-0806 | MicrosoftInternet Explorer CISA KEV | fix due 2026-06-03 | Duration unknown |
| 2026-05-20 | Added to CISA KEV | MicrosoftDefender | fix due 2026-06-03 | Duration unknown | |
| 2026-05-20 | same kind of change as the line above | CVE-2026-41091 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-05-20 | same kind of change as the line above | CVE-2026-45498 | same vendor as the line above | same change as the line above | Duration unknown |
| Fri 15 May 2026· 2 changes | |||||
| 2026-05-15 | Added to CISA KEV | CVE-2026-42897 | MicrosoftMicrosoft CISA KEV | fix due 2026-05-29 | Duration unknown |
| 2026-05-15 | Product added | CVE-2026-40379 | not named as affected at publication, now names microsoft entra | Time to revision 3 days | |
| Thu 14 May 2026· 5 changes | |||||
| 2026-05-14 | Product added | CVE-2026-35433 | not named as affected at publication, now names microsoft .net framework 3.5 and 4 more | Time to revision 2 days | |
| 2026-05-14 | same kind of change as the line above | CVE-2026-35433 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 | Time to revision 2 days |
| 2026-05-14 | same kind of change as the line above | CVE-2026-35433 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 2 days |
| 2026-05-14 | same kind of change as the line above | CVE-2026-35433 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 2 days |
| 2026-05-14 | same kind of change as the line above | CVE-2026-35433 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 2 days |
| 2026-05-14 | same kind of change as the line above | CVE-2026-35433 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 4.8 | Time to revision 2 days |
| Wed 13 May 2026· 2 changes | |||||
| 2026-05-13 | Fix version moved | microsoftmicrosoft dynamics 365 (on-premises) version 9.1 | stated at publication 9.1.44.15, now states 9.1.45.11Release branch starts at 9.0.same day | Time to revision 1 days | |
| 2026-05-13 | same kind of change as the line above | CVE-2026-42898 | same vendor as the line above | same change as the line aboveRelease branch starts at 9.0.same day | Time to revision 1 days |
| 2026-05-13 | same kind of change as the line above | CVE-2026-42833 | same vendor as the line above | same change as the line aboveRelease branch starts at 9.0.same day | Time to revision 1 days |
| Mon 11 May 2026· 5 changes | |||||
| 2026-05-11 | Fix version moved | CVE-2026-21523 | microsoftvisual studio code | stated at publication 1.109.2, now states 1.110.1Release branch starts at 1.0.0. | Time to revision 90 days |
| 2026-05-11 | Fix version moved | CVE-2026-20841 | microsoftwindows notepad | stated at publication 11.2510, now states 11.2512.26.0Release branch starts at 11.0.0.Original value first replaced 2026-03-12; this value first seen 2026-05-11. | Time to revision 30 days |
| 2026-05-11 | Product added | CVE-2026-32226 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 and 2 more | Time to revision 27 days | |
| 2026-05-11 | same kind of change as the line above | CVE-2026-32226 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 27 days |
| 2026-05-11 | same kind of change as the line above | CVE-2026-32226 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 4.7.2 | Time to revision 27 days |
| 2026-05-11 | same kind of change as the line above | CVE-2026-32226 | same vendor as the line above | not named as affected at publication, now names microsoft .net framework 4.8.1 | Time to revision 27 days |
| Tue 28 Apr 2026· 2 changes | |||||
| 2026-04-28 | Added to CISA KEV | CVE-2026-32202 | MicrosoftWindows CISA KEV | fix due 2026-05-12 | Duration unknown |
| 2026-04-28 | Product added | CVE-2026-40372 | not named as affected at publication, now names microsoft visual studio 2026 version 18.5 | Time to revision 7 days | |
| Wed 22 Apr 2026· 3 changes | |||||
| 2026-04-22 | Added to CISA KEV | CVE-2026-33825 | MicrosoftDefender CISA KEV | fix due 2026-05-06 | Duration unknown |
| 2026-04-22 | Product added | CVE-2026-26171 | not named as affected at publication, now names powershell 7.5 and 1 more | Time to revision 8 days | |
| 2026-04-22 | same kind of change as the line above | CVE-2026-26171 | same vendor as the line above | not named as affected at publication, now names powershell 7.5 | Time to revision 8 days |
| 2026-04-22 | same kind of change as the line above | CVE-2026-26171 | same vendor as the line above | not named as affected at publication, now names powershell 7.6 | Time to revision 8 days |
| Tue 21 Apr 2026· 2 changes | |||||
| 2026-04-21 | Ransomware use confirmed | CVE-2023-21529 | MicrosoftExchange Server CISA KEV | stated at publication Unknown, now states Known | Time to revision 8 days |
| 2026-04-21 | Product added | CVE-2026-32203 | not named as affected at publication, now names microsoft visual studio 2026 version 18.4 | Time to revision 7 days | |
| Tue 14 Apr 2026· 2 changes | |||||
| 2026-04-14 | Added to CISA KEV | CVE-2009-0238 | MicrosoftOffice CISA KEV | fix due 2026-04-28 | Duration unknown |
| 2026-04-14 | Added to CISA KEV | CVE-2026-32201 | MicrosoftSharePoint Server CISA KEV | fix due 2026-04-28 | Duration unknown |
| Mon 13 Apr 2026· 4 changes | |||||
| 2026-04-13 | Added to CISA KEV | CVE-2012-1854 | MicrosoftVisual Basic for Applications (VBA) CISA KEV | fix due 2026-04-27 | Duration unknown |
| 2026-04-13 | Added to CISA KEV | MicrosoftWindows | fix due 2026-04-27 | Duration unknown | |
| 2026-04-13 | same kind of change as the line above | CVE-2025-60710 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-04-13 | same kind of change as the line above | CVE-2023-36424 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-04-13 | Added to CISA KEV | CVE-2023-21529 | MicrosoftExchange Server CISA KEV | fix due 2026-04-27 | Duration unknown |
| Fri 10 Apr 2026· 1 change | |||||
| 2026-04-10 | Fix version moved | CVE-2026-21518 | microsoftvisual studio code | stated at publication 1.109.2, now states 1.110.1Release branch starts at 1.0.0. | Time to revision 59 days |
| Fri 27 Mar 2026· 1 change | |||||
| 2026-03-27 | Product added | CVE-2026-26137 | not named as affected at publication, now names microsoft exchange online | Time to revision 8 days | |
| Mon 23 Mar 2026· 2 changes | |||||
| 2026-03-23 | Product added | CVE-2026-25166 | not named as affected at publication, now names windows adk for windows 10, version 2004 and 1 more | Time to revision 13 days | |
| 2026-03-23 | same kind of change as the line above | CVE-2026-25166 | same vendor as the line above | not named as affected at publication, now names windows adk for windows 10, version 2004 | Time to revision 13 days |
| 2026-03-23 | same kind of change as the line above | CVE-2026-25166 | same vendor as the line above | not named as affected at publication, now names windows adk for windows 11, version 22h2 | Time to revision 13 days |
| Wed 18 Mar 2026· 1 change | |||||
| 2026-03-18 | Added to CISA KEV | CVE-2026-20963 | MicrosoftSharePoint CISA KEV | fix due 2026-03-21 | Duration unknown |
| Fri 13 Mar 2026· 21 changes | |||||
| 2026-03-133 commits | Product added | 21 rows, one per record and product | not named as affected at publication, now names windows 10 version 1607 and 10 moreBranches and original-value intervals are stated on each row. | Time to revision 3 to 31 days | |
| 2026-03-13 | same kind of change as the line above | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 10 version 1607 | Time to revision 3 days |
| 2026-03-13 | same kind of change as the line above | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 10 version 1809 | Time to revision 3 days |
| 2026-03-13 | same kind of change as the line above | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 10 version 21h2 | Time to revision 3 days |
| 2026-03-13 | same kind of change as the line above | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 10 version 22h2 | Time to revision 3 days |
| 2026-03-13 | same kind of change as the line above | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 11 version 22h3 | Time to revision 3 days |
| 2026-03-13 | same kind of change as the line above | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 11 version 23h2 | Time to revision 3 days |
| 2026-03-13 | same kind of change as the line above | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 11 version 24h2 | Time to revision 3 days |
| 2026-03-13 | same kind of change as the line above | CVE-2026-25172 | same vendor as the line above | not named as affected at publication, now names windows 11 version 25h2 | Time to revision 3 days |
| 13 more rows in this change are not listed here. Open all 21 rows → | |||||
| Fri 27 Feb 2026· 2 changes | |||||
| 2026-02-272 commits | Product added | not named as affected at publication, now names microsoft visual studio code copilot chat extensionBranches and original-value intervals are stated on each row. | Time to revision 17 days | ||
| 2026-02-27 | same kind of change as the line above | CVE-2026-21523 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| 2026-02-27 | same kind of change as the line above | CVE-2026-21518 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| Tue 17 Feb 2026· 1 change | |||||
| 2026-02-17 | Added to CISA KEV | CVE-2008-0015 | MicrosoftWindows CISA KEV | fix due 2026-03-10 | Duration unknown |
| Fri 13 Feb 2026· 3 changes | |||||
| 2026-02-13 | Product added | CVE-2025-21264 | not named as affected at publication, now names microsoft visual studio code copilot chat extension | Time to revision 276 days | |
| 2026-02-13 | Product added | CVE-2025-27488 | not named as affected at publication, now names windows hlk, version 1809 | Time to revision 276 days | |
| 2026-02-13 | Product added | CVE-2025-47733 | not named as affected at publication, now names microsoft power pages | Time to revision 281 days | |
| Thu 12 Feb 2026· 1 change | |||||
| 2026-02-12 | Added to CISA KEV | CVE-2024-43468 | MicrosoftConfiguration Manager CISA KEV | fix due 2026-03-05 | Duration unknown |
| Tue 10 Feb 2026· 6 changes | |||||
| 2026-02-10 | Added to CISA KEV | MicrosoftWindows | fix due 2026-03-03 | Duration unknown | |
| 2026-02-10 | same kind of change as the line above | CVE-2026-21513 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-02-10 | same kind of change as the line above | CVE-2026-21525 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-02-10 | same kind of change as the line above | CVE-2026-21510 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-02-10 | same kind of change as the line above | CVE-2026-21533 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-02-10 | same kind of change as the line above | CVE-2026-21519 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-02-10 | Added to CISA KEV | CVE-2026-21514 | MicrosoftOffice CISA KEV | fix due 2026-03-03 | Duration unknown |
| Thu 29 Jan 2026· 2 changes | |||||
| 2026-01-29 | Ransomware use confirmed | CVE-2024-49039 | MicrosoftWindows CISA KEV | stated at publication Unknown, now states Known | Duration unknown |
| 2026-01-29 | Ransomware use confirmed | CVE-2024-30088 | MicrosoftWindows CISA KEV | stated at publication Unknown, now states Known | Duration unknown |
| Mon 26 Jan 2026· 1 change | |||||
| 2026-01-26 | Added to CISA KEV | CVE-2026-21509 | MicrosoftOffice CISA KEV | fix due 2026-02-16 | Duration unknown |
| Tue 13 Jan 2026· 1 change | |||||
| 2026-01-13 | Added to CISA KEV | CVE-2026-20805 | MicrosoftWindows CISA KEV | fix due 2026-02-03 | Duration unknown |
| Wed 7 Jan 2026· 1 change | |||||
| 2026-01-07 | Added to CISA KEV | CVE-2009-0556 | MicrosoftOffice CISA KEV | fix due 2026-01-28 | Duration unknown |
| Tue 9 Dec 2025· 5 changes | |||||
| 2025-12-09 | Added to CISA KEV | CVE-2025-62221 | MicrosoftWindows CISA KEV | fix due 2025-12-30 | Duration unknown |
| 2025-12-09 | Fix version moved | CVE-2025-60710 | microsoftwindows 11 version 25h2 | stated at publication 10.0.26200.7171, now states 10.0.26200.7462Release branch starts at 10.0.26200.0. | Time to revision 28 days |
| 2025-12-09 | Product added | CVE-2025-60710 | not named as affected at publication, now names windows 11 version 24h2 and 2 more | Time to revision 28 days | |
| 2025-12-09 | same kind of change as the line above | CVE-2025-60710 | same vendor as the line above | not named as affected at publication, now names windows 11 version 24h2 | Time to revision 28 days |
| 2025-12-09 | same kind of change as the line above | CVE-2025-60710 | same vendor as the line above | not named as affected at publication, now names windows server 2025 | Time to revision 28 days |
| 2025-12-09 | same kind of change as the line above | CVE-2025-60710 | same vendor as the line above | not named as affected at publication, now names windows server 2025 (server core installation) | Time to revision 28 days |
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
What this page cannot see
Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
The units, the refusals, the cut-offs and every source, in full →
Paste your closed CVE tickets and see which of these changes hit them →