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 21 Aug 2026· 1 change | ||||
| 2026-08-21 | CVE-2026-18952 | githubopensearch AMZN | stated at publication 3.5.0, now states 3.7.0Release branch starts at 2.15.0. | Time to revision 9 days |
| Thu 20 Aug 2026· 1 change | ||||
| 2026-08-20 | CVE-2026-17561 | TR-CERT | stated at publication 6.4.108, now states 6.4.115Release branch starts at 0. | Time to revision 20 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 11 Aug 2026· 2 changes | ||||
| 2026-08-11 | usmannasircyberpanel VulnCheck | stated at publication 2.4.4, now states 2.4.5Release branch starts at 0. | Time to revision 109 days | |
| 2026-08-11 | CVE-2026-41472 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 109 days |
| 2026-08-11 | CVE-2026-41473 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 109 days |
| Sat 8 Aug 2026· 1 change | ||||
| 2026-08-08 | CVE-2025-4106 | watchguardfireware os | stated at publication 12.11.2, now states 12.11.3Release branch starts at 12.0. | Time to revision 287 days |
| Fri 7 Aug 2026· 4 changes | ||||
| 2026-08-07 | CVE-2026-68480 | linuxlinux | stated at publication 5.10.263, now states 5.10.264Release branch starts at 5.10.*.same day | Time to revision 1 days |
| 2026-08-07 | CVE-2026-68480 | linuxlinux | stated at publication 5.15.214, now states 5.15.215Release branch starts at 5.15.*.same day | Time to revision 1 days |
| 2026-08-07 | CVE-2026-68480 | linuxlinux | stated at publication 6.1.181, now states 6.1.182Release branch starts at 6.1.*.same day | Time to revision 1 days |
| 2026-08-07 | CVE-2026-68480 | linuxlinux | stated at publication 6.6.149, now states 6.6.150Release branch starts at 6.6.*.same day | Time to revision 1 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 |
| Fri 24 Jul 2026· 1 change | ||||
| 2026-07-24 | CVE-2026-8661 | rapid7insightconnect markdown plugin | stated at publication 4.0.0, now states 4.0.2Release branch starts at 4.0.0. | Time to revision 28 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 → | ||||
| Tue 21 Jul 2026· 1 change | ||||
| 2026-07-21 | CVE-2026-64824 | home-assistanthome assistant core VulnCheck | stated at publication 2026.6.0, now states 2026.7.0Release branch starts at 0.same day | Time to revision 0 days |
| Wed 1 Jul 2026· 1 change | ||||
| 2026-07-01 | CVE-2026-13006 | qos.ch sarllogback-core NCSC.ch | stated at publication 1.5.35, now states 1.5.37Release branch starts at 1.5.35.Original value first replaced 2026-06-24; this value first seen 2026-07-01.same day | Time to revision 0 days |
| Mon 29 Jun 2026· 1 change | ||||
| 2026-06-29 | CVE-2026-2587 | eclipse foundationeclipse glassfish eclipse | stated at publication 7.1.0, now states 7.1.1Release branch starts at 0.Original value first replaced 2026-05-20; this value first seen 2026-06-29.same day | Time to revision 1 days |
| Thu 25 Jun 2026· 1 change | ||||
| 2026-06-25 | CVE-2026-33813 | golang.org/x/imagegolang.org/x/image/webp Go | stated at publication 0.39.0, now states 0.42.0Release branch starts at 0. | Time to revision 65 days |
| Tue 23 Jun 2026· 2 changes | ||||
| 2026-06-23 | CVE-2026-56784 | openremoteopenremote VulnCheck | stated at publication 1.24.2, now states 1.25.0Release branch starts at 0.same day | Time to revision 0 days |
| 2026-06-23 | CVE-2026-41715 | springreactor netty vmware | stated at publication 1.3.6, now states 1.3.15.1Release branch starts at 1.3.0. | Time to revision 15 days |
| Fri 19 Jun 2026· 4 changes | ||||
| 2026-06-19 | CVE-2026-43064 | linuxlinux | stated at publication 6.1.168, now states 6.1.176Release branch starts at 6.1.*.Original value first replaced 2026-06-01; this value first seen 2026-06-19. | Time to revision 27 days |
| 2026-06-19 | CVE-2026-45852 | linuxlinux | stated at publication 5.10.252, now states 5.10.259Release branch starts at 5.10.*. | Time to revision 23 days |
| 2026-06-19 | CVE-2026-45852 | linuxlinux | stated at publication 5.15.202, now states 5.15.210Release branch starts at 5.15.*. | Time to revision 23 days |
| 2026-06-19 | CVE-2026-45852 | linuxlinux | stated at publication 6.1.165, now states 6.1.176Release branch starts at 6.1.*. | Time to revision 23 days |
| Wed 17 Jun 2026· 2 changes | ||||
| 2026-06-17 | qnap systems inc.qumagie qnap | stated at publication 2.9.0, now states 2.9.1Release branch starts at 2.9.0. | Time to revision 7 to 8 days | |
| 2026-06-17 | CVE-2026-26236 | same vendor as the line above | same change as the line aboveRelease branch starts at 2.9.0. | Time to revision 8 days |
| 2026-06-17 | CVE-2026-26237 | same vendor as the line above | same change as the line aboveRelease branch starts at 2.9.0. | Time to revision 7 days |
| 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 |
| Mon 8 Jun 2026· 1 change | ||||
| 2026-06-08 | CVE-2026-49777 | shapedplugin, llcproduct slider pro for woocommerce Patchstack | stated at publication 3.5.3, now states 3.5.4Release branch starts at 0. | Time to revision 3 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 |
| Thu 21 May 2026· 1 change | ||||
| 2026-05-21 | CVE-2026-48172 | litespeed technologiescpanel plugin mitre | stated at publication 2.4.5, now states 2.4.7Release branch starts at 2.3.same day | Time to revision 1 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 |
| Mon 4 May 2026· 2 changes | ||||
| 2026-05-04 | CVE-2026-5161 | TR-CERT | stated at publication v1.2.1, now states 1.2.2Release branch starts at 0. | Time to revision 5 days |
| 2026-05-04 | CVE-2026-23112 | linuxlinux | stated at publication 5.10.250, now states 5.10.253Release branch starts at 5.10.*. | Time to revision 80 days |
| Fri 17 Apr 2026· 6 changes | ||||
| 2026-04-17 | CVE-2026-3854 | githubenterprise server GitHub_P | stated at publication 3.14.24, now states 3.14.25Release branch starts at 3.14.0. | Time to revision 38 days |
| 2026-04-17 | CVE-2026-3854 | githubenterprise server GitHub_P | stated at publication 3.15.19, now states 3.15.20Release branch starts at 3.15.0. | Time to revision 38 days |
| 2026-04-17 | CVE-2026-3854 | githubenterprise server GitHub_P | stated at publication 3.16.15, now states 3.16.16Release branch starts at 3.16.0. | Time to revision 38 days |
| 2026-04-17 | CVE-2026-3854 | githubenterprise server GitHub_P | stated at publication 3.17.12, now states 3.17.13Release branch starts at 3.17.0. | Time to revision 38 days |
| 2026-04-17 | CVE-2026-3854 | githubenterprise server GitHub_P | stated at publication 3.18.6, now states 3.18.7Release branch starts at 3.18.0. | Time to revision 38 days |
| 2026-04-17 | CVE-2026-3854 | githubenterprise server GitHub_P | stated at publication 3.19.3, now states 3.19.4Release branch starts at 3.19.0. | Time to revision 38 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 |
| Fri 3 Apr 2026· 6 changes | ||||
| 2026-04-03 | CVE-2025-40219 | linuxlinux | stated at publication 5.10.246, now states 5.10.252Release branch starts at 5.10.*. | Time to revision 120 days |
| 2026-04-03 | CVE-2025-40219 | linuxlinux | stated at publication 5.15.195, now states 5.15.202Release branch starts at 5.15.*. | Time to revision 120 days |
| 2026-04-03 | CVE-2025-40219 | linuxlinux | stated at publication 6.1.157, now states 6.1.165Release branch starts at 6.1.*. | Time to revision 120 days |
| 2026-04-03 | CVE-2025-40219 | linuxlinux | stated at publication 6.12.54, now states 6.12.75Release branch starts at 6.12.*. | Time to revision 120 days |
| 2026-04-03 | CVE-2025-40219 | linuxlinux | stated at publication 6.6.113, now states 6.6.128Release branch starts at 6.6.*. | Time to revision 120 days |
| 2026-04-03 | CVE-2025-40219 | linuxlinux | stated at publication 6.18, now states 6.18.16Release branch starts at *. | Duration unknown |
| Thu 2 Apr 2026· 2 changes | ||||
| 2026-04-02 | CVE-2025-24213 | appleipados | stated at publication 17.7, now states 17.7.7Release branch starts at 0. | Time to revision 367 days |
| 2026-04-02 | CVE-2025-24220 | appleipados | stated at publication 17.7, now states 17.7.9Release branch starts at 0.Original value first replaced 2025-05-20; this value first seen 2026-04-02. | Time to revision 8 days |
| Wed 1 Apr 2026· 1 change | ||||
| 2026-04-01 | CVE-2024-54254 | kofi mokomemessage filter for contact form 7 Patchstack | stated at publication 1.6.3, now states 1.6.3.1Release branch starts at 1.6.bulk ×86 | Time to revision 478 days |
| Mon 30 Mar 2026· 1 change | ||||
| 2026-03-30 | CVE-2025-13611 | gitlabgitlab | stated at publication 18.6.1, now states 18.6.3Release branch starts at 18.6. | Time to revision 124 days |
| Fri 27 Mar 2026· 1 change | ||||
| 2026-03-27 | CVE-2026-2339 | TR-CERT | stated at publication v3.4.0, now states 3.5.1Release branch starts at 0. | Time to revision 17 days |
| Wed 4 Mar 2026· 1 change | ||||
| 2026-03-04 | CVE-2025-53868 | f5big-ip | stated at publication 17.1.3, now states 17.1.3.1Release branch starts at 17.1.0. | Time to revision 140 days |
| Wed 18 Feb 2026· 4 changes | ||||
| 2026-02-18 | kubernetesingress-nginx | stated at publication 1.14.2, now states 1.14.3Release branch starts at 0. | Time to revision 15 days | |
| 2026-02-18 | CVE-2026-1580 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 15 days |
| 2026-02-18 | CVE-2026-24512 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 15 days |
| 2026-02-18 | CVE-2026-24513 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 15 days |
| 2026-02-18 | CVE-2026-24514 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 15 days |
| Tue 27 Jan 2026· 1 change | ||||
| 2026-01-27 | CVE-2025-14756 | tp-link systems inc.archer mr600 v5.0 TPLink | stated at publication 1.0.0 0.9.1 v0001.0 Build 250930 Rel.63611n, now states 1.1.0 0.9.1 v0001.0 Build 250930 Rel.63611nRelease branch starts at 0.same day | Time to revision 0 days |
| Fri 19 Dec 2025· 10 changes | ||||
| 2025-12-19 | VulnCheck | stated at publication 20.0, now states 20.1Release branch starts at 0. | Time to revision 2 days | |
| 2025-12-19 | CVE-2025-34441 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | CVE-2025-34442 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | CVE-2025-34440 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | CVE-2025-34439 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | CVE-2025-34434 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | CVE-2025-34436 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | CVE-2025-34435 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | CVE-2025-34437 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 1 more row in this change is not listed here. Open all 9 rows → | ||||
| 2025-12-19 | CVE-2025-14318 | m-files corporationm-files server | stated at publication 25.12, now states 25.12.15491.7Release branch starts at 0.same day | Time to revision 1 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 |
| Tue 2 Dec 2025· 5 changes | ||||
| 2025-12-02 | CVE-2025-11578 | githubenterprise server GitHub_P | stated at publication 3.14.19, now states 3.14.20Release branch starts at 3.14. | Time to revision 22 days |
| 2025-12-02 | CVE-2025-11578 | githubenterprise server GitHub_P | stated at publication 3.15.14, now states 3.15.15Release branch starts at 3.15. | Time to revision 22 days |
| 2025-12-02 | CVE-2025-11578 | githubenterprise server GitHub_P | stated at publication 3.16.10, now states 3.16.11Release branch starts at 3.16. | Time to revision 22 days |
| 2025-12-02 | CVE-2025-11578 | githubenterprise server GitHub_P | stated at publication 3.17.7, now states 3.17.8Release branch starts at 3.17. | Time to revision 22 days |
| 2025-12-02 | CVE-2025-11578 | githubenterprise server GitHub_P | stated at publication 3.18.1, now states 3.18.2Release branch starts at 3.18. | Time to revision 22 days |
| Thu 20 Nov 2025· 8 changes | ||||
| 2025-11-20 | soplanningsoplanning CERT-PL | stated at publication 1.54, now states 1.55Release branch starts at 0.same day | Time to revision 0 days | |
| 2025-11-20 | CVE-2025-62293 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| 2025-11-20 | CVE-2025-62294 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| 2025-11-20 | CVE-2025-62295 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| 2025-11-20 | CVE-2025-62296 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| 2025-11-20 | CVE-2025-62297 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| 2025-11-20 | CVE-2025-62729 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| 2025-11-20 | CVE-2025-62730 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| 2025-11-20 | CVE-2025-62731 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 0 days |
| Tue 11 Nov 2025· 4 changes | ||||
| 2025-11-112 commits | salesforceagentforce vibes extension | stated at publication 3.2.0, now states 3.3.0Branches and original-value intervals are stated on each row. | Time to revision 6 to 7 days | |
| 2025-11-11 | CVE-2025-64322 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 7 days |
| 2025-11-11 | CVE-2025-64321 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 6 days |
| 2025-11-112 commits | salesforcemulesoft anypoint code builder | stated at publication 1.11.6, now states 1.12.1Branches and original-value intervals are stated on each row. | Time to revision 6 to 7 days | |
| 2025-11-11 | CVE-2025-64319 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 7 days |
| 2025-11-11 | CVE-2025-64318 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 6 days |
| Thu 30 Oct 2025· 1 change | ||||
| 2025-10-30 | CVE-2025-43939 | dellunity | stated at publication 5.4, now states 5.5.2Release branch starts at 0.same day | Time to revision 0 days |
| Wed 29 Oct 2025· 1 change | ||||
| 2025-10-29 | CVE-2025-41443 | mattermostmattermost | stated at publication 10.5.11, now states 10.5.13Release branch starts at 10.5.0. | Time to revision 13 days |
| Thu 23 Oct 2025· 4 changes | ||||
| 2025-10-23 | CVE-2025-6203 | hashicorpvault | stated at publication 1.20.2, now states 1.21.0Release branch starts at 1.15.0. | Time to revision 56 days |
| 2025-10-23 | CVE-2025-6203 | hashicorpvault enterprise | stated at publication 1.16.25, now states 1.16.27Release branch starts at 1.16. | Time to revision 56 days |
| 2025-10-23 | CVE-2025-6203 | hashicorpvault enterprise | stated at publication 1.19.9, now states 1.19.11Release branch starts at 1.19. | Time to revision 56 days |
| 2025-10-23 | CVE-2025-6203 | hashicorpvault enterprise | stated at publication 1.20.2, now states 1.20.5Release branch starts at 0. | Time to revision 56 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 |
| Thu 2 Oct 2025· 7 changes | ||||
| 2025-10-02 | CVE-2025-38709 | linuxlinux | stated at publication 6.6.103, now states 6.6.109Release branch starts at 6.6.*.Original value first replaced 2025-09-25; this value first seen 2025-10-02. | Time to revision 21 days |
| 2025-10-02 | CVE-2023-53431 | linuxlinux | stated at publication 4.19.276, now states 4.19.281Release branch starts at 4.19.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | CVE-2023-53431 | linuxlinux | stated at publication 5.10.173, now states 5.10.178Release branch starts at 5.10.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | CVE-2023-53431 | linuxlinux | stated at publication 5.15.99, now states 5.15.108Release branch starts at 5.15.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | CVE-2023-53431 | linuxlinux | stated at publication 5.4.235, now states 5.4.241Release branch starts at 5.4.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | CVE-2023-53431 | linuxlinux | stated at publication 6.1.16, now states 6.1.25Release branch starts at 6.1.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | CVE-2023-53431 | linuxlinux | stated at publication 6.2.3, now states 6.2.12Release branch starts at 6.2.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| Wed 24 Sep 2025· 1 change | ||||
| 2025-09-24 | CVE-2025-10630 | grafanagrafana-zabbix-plugin | stated at publication 6.0.0, now states 6.0.2Release branch starts at 0. | Time to revision 5 days |
| Tue 9 Sep 2025· 6 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 |
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 →