Every fix version that moved
| Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin. | Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on. | Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry. | What 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 2 Sep 2026· 9 changes | ||||
| 2026-09-02 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 14 Aug 2026· 18 changes | ||||
| 2026-08-14 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| Tue 28 Jul 2026· 28 changes | ||||
| 2026-07-28 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| Wed 22 Jul 2026· 11 changes | ||||
| 2026-07-222 commits | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 → | ||||
| Mon 15 Jun 2026· 3 changes | ||||
| 2026-06-15 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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· 54 changes | ||||
| 2026-06-09 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| Fri 5 Jun 2026· 1 change | ||||
| 2026-06-05 | 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 13 May 2026· 2 changes | ||||
| 2026-05-13 | 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 | 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 | 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· 2 changes | ||||
| 2026-05-11 | 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 | 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 |
| Fri 10 Apr 2026· 1 change | ||||
| 2026-04-10 | 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 |
| Tue 9 Dec 2025· 1 change | ||||
| 2025-12-09 | 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 |
| Wed 15 Oct 2025· 1 change | ||||
| 2025-10-15 | 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 |
| Tue 9 Sep 2025· 16 changes | ||||
| 2025-09-09 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| Tue 12 Aug 2025· 1 change | ||||
| 2025-08-12 | 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 |
| Fri 11 Jul 2025· 1 change | ||||
| 2025-07-11 | 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· 2 changes | ||||
| 2025-07-08 | 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 | 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 |
| Thu 22 May 2025· 1 change | ||||
| 2025-05-22 | 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 |
| Tue 11 Mar 2025· 1 change | ||||
| 2025-03-11 | 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 |
| Tue 11 Feb 2025· 1 change | ||||
| 2025-02-11 | 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 |
| Tue 31 Dec 2024· 3 changes | ||||
| 2024-12-31 | 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 | 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 | 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 |
| Tue 10 Dec 2024· 6 changes | ||||
| 2024-12-10 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| Wed 27 Nov 2024· 3 changes | ||||
| 2024-11-27 | 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 | 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 | 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 |
| Tue 8 Oct 2024· 2 changes | ||||
| 2024-10-08 | 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 | 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 |
| Thu 19 Sep 2024· 2 changes | ||||
| 2024-09-19 | 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 | 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 | 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· 1 change | ||||
| 2024-09-10 | 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 |
| Tue 9 Jul 2024· 1 change | ||||
| 2024-07-09 | 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 |
| Thu 13 Jun 2024· 1 change | ||||
| 2024-06-13 | 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· 1 change | ||||
| 2024-05-15 | 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 |
| Tue 14 May 2024· 5 changes | ||||
| 2024-05-14 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| Fri 22 Mar 2024· 1 change | ||||
| 2024-03-22 | CVE-2024-21388 | microsoftmicrosoft edge (chromium-based) | stated at publication 121.0.2277.83, now states 121.0.2277.98Release branch starts at 1.0.0. | Time to revision 52 days |
| Thu 30 Nov 2023· 1 change | ||||
| 2023-11-30 | CVE-2023-36796 | microsoftmicrosoft visual studio 2022 version 17.7 | stated at publication 17.7.4, now states 17.7.6Release branch starts at 17.7.0.Original value first replaced 2023-11-06; this value first seen 2023-11-30. | Time to revision 55 days |
| Mon 6 Nov 2023· 24 changes | ||||
| 2023-11-06 | microsoft.net 6.0 | stated at publication 6.0.22, now states 6.0.24Release branch starts at 6.0.0. | Time to revision 55 days | |
| 2023-11-06 | CVE-2023-36799 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.0.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36796 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.0.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36794 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.0.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36793 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.0.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36792 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.0.0. | Time to revision 55 days |
| 2023-11-06 | microsoft.net 7.0 | stated at publication 7.0.11, now states 7.0.13Release branch starts at 7.0.0. | Time to revision 55 days | |
| 2023-11-06 | CVE-2023-36799 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36796 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36794 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36793 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36792 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Time to revision 55 days |
| 2023-11-06 | microsoftmicrosoft visual studio 2022 version 17.2 | stated at publication 17.2.19, now states 17.2.21Release branch starts at 17.2.0. | Time to revision 55 days | |
| 2023-11-06 | CVE-2023-36799 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.2.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36796 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.2.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36794 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.2.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36793 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.2.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36792 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.2.0. | Time to revision 55 days |
| 2023-11-06 | microsoftmicrosoft visual studio 2022 version 17.4 | stated at publication 17.4.11, now states 17.4.13Release branch starts at 17.4.0. | Time to revision 55 days | |
| 2023-11-06 | CVE-2023-36799 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.4.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36796 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.4.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36794 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.4.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36793 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.4.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36792 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.4.0. | Time to revision 55 days |
| 2023-11-06 | microsoftmicrosoft visual studio 2022 version 17.6 | stated at publication 17.6.7, now states 17.6.9Release branch starts at 17.6.0. | Time to revision 55 days | |
| 2023-11-06 | CVE-2023-36799 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.6.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36796 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.6.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36794 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.6.0. | Time to revision 55 days |
| 2023-11-06 | CVE-2023-36793 | same vendor as the line above | same change as the line aboveRelease branch starts at 17.6.0. | Time to revision 55 days |
| Tue 12 Sep 2023· 2 changes | ||||
| 2023-09-12 | microsoftmicrosoft dynamics 365 (on-premises) version 9.0 | stated at publication 9.0.47.xx, now states 9.0.49.04Release branch starts at 9.0.0.same day | Time to revision 0 days | |
| 2023-09-12 | CVE-2023-36886 | same vendor as the line above | same change as the line aboveRelease branch starts at 9.0.0.same day | Time to revision 0 days |
| 2023-09-12 | CVE-2023-38164 | same vendor as the line above | same change as the line aboveRelease branch starts at 9.0.0.same day | Time to revision 0 days |
| Mon 5 Jun 2023· 2 changes | ||||
| 2023-06-05 | microsoftav1 video extension | stated at publication 1.1.51091.0, now states 1.1.60961.0Release branch starts at 1.1.0. | Time to revision 27 days | |
| 2023-06-05 | CVE-2023-29340 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.1.0. | Time to revision 27 days |
| 2023-06-05 | CVE-2023-29341 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.1.0. | Time to revision 27 days |
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller. 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 →