Every fix version that moved

Compare earlier and later source statements, with the dates and evidence behind each measured change.

31 changes · newest first · grouped by dayCSV JSON RSS

SinceKindVendorSortClear all

Counted changes of "Fix version moved" from the last 30 days, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.	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	Show all 8 CVE records in this change: Fix version moved: 1.132.1 → 1.135 from microsoftHide the 8 CVE records in this change: Fix version moved: 1.132.1 → 1.135 from microsoft	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	innotim software, telecommunications and consulting trade ltd. co.logsign siem 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-32202Show all 3 products in this change: Fix version moved: 10.0.14393.9060 → 10.0.14393.9339 in CVE-2026-32202Hide the 3 products in this change: Fix version moved: 10.0.14393.9060 → 10.0.14393.9339 in 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-32202Show all 3 products in this change: Fix version moved: 10.0.17763.8644 → 10.0.17763.9020 in CVE-2026-32202Hide the 3 products in this change: Fix version moved: 10.0.17763.8644 → 10.0.17763.9020 in 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-32202Show all 2 products in this change: Fix version moved: 6.2.9200.26026 → 6.2.9200.26226 in CVE-2026-32202Hide the 2 products in this change: Fix version moved: 6.2.9200.26026 → 6.2.9200.26226 in 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-32202Show all 2 products in this change: Fix version moved: 6.3.9600.23132 → 6.3.9600.23291 in CVE-2026-32202Hide the 2 products in this change: Fix version moved: 6.3.9600.23132 → 6.3.9600.23291 in 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-32202Show all 2 products in this change: Fix version moved: 10.0.26100.32690 → 10.0.26100.33158 in CVE-2026-32202Hide the 2 products in this change: Fix version moved: 10.0.26100.32690 → 10.0.26100.33158 in 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	Show all 2 CVE records in this change: Fix version moved: 2.4.4 → 2.4.5 from usmannasirHide the 2 CVE records in this change: Fix version moved: 2.4.4 → 2.4.5 from usmannasir	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

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.

4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

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 →