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. |
|---|---|---|---|---|---|
| Thu 3 Sep 2026· 1 record change | |||||
| 2026-09-03 | Product added | CVE-2026-58641 | not named as affected at publication, now names skiasharp | Days to revision 23 | |
| Wed 2 Sep 2026· 9 record 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. | Days to revision 17 |
| 2026-09-02 | Fix version moved | CVE-2026-58650 | 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. | Days to revision 17 |
| 2026-09-02 | Fix version moved | CVE-2026-59113 | 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. | Days to revision 17 |
| 2026-09-02 | Fix version moved | CVE-2026-47285 | 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. | Days to revision 17 |
| 2026-09-02 | Fix version moved | CVE-2026-69320 | 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. | Days to revision 17 |
| 2026-09-02 | Fix version moved | CVE-2026-69278 | 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. | Days to revision 17 |
| 2026-09-02 | Fix version moved | CVE-2026-69306 | 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. | Days to revision 17 |
| 2026-09-02 | Fix version moved | CVE-2026-70335 | 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. | Days to revision 17 |
| 2026-09-02 | Fix version moved | CVE-2026-70336 | 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. | Days to revision 17 |
| Fri 28 Aug 2026· 1 record change | |||||
| 2026-08-28 | Product added | CVE-2026-59133 | not named as affected at publication, now names microsoft hpc pack 2019 | Days to revision 17 | |
| Thu 27 Aug 2026· 1 record change | |||||
| 2026-08-27 | CVSS base score changed | CVE-2026-65660 | whole record microsoft | stated at publication 6.5, now states 8.8CVSS v3.1 · base scoreMediumHigh | Days to revision 16 |
| Thu 20 Aug 2026· 2 record changes | |||||
| 2026-08-20 | CVSS base score changed | CVE-2026-54117 | whole record microsoft | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Days to revision 37 |
| 2026-08-20 | CVSS base score changed | CVE-2026-54118 | whole record microsoft | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Days to revision 37 |
| Sun 16 Aug 2026· 1 record change | |||||
| 2026-08-16 | Product added | CVE-2026-59124 | not named as affected at publication, now names microsoft hpc pack 2019 | Days to revision 5 | |
| Fri 14 Aug 2026· 19 record changes | |||||
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 10 version 1607 | stated at publication 10.0.14393.9060, now states 10.0.14393.9339Release branch starts at 10.0.14393.0. | Days to revision 122 |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 10 version 1809 | stated at publication 10.0.17763.8644, now states 10.0.17763.9020Release branch starts at 10.0.17763.0. | Days to revision 122 |
| 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. | Days to revision 122 |
| 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. | Days to revision 122 |
| 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. | Days to revision 122 |
| 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. | Days to revision 122 |
| 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. | Days to revision 122 |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2012 | stated at publication 6.2.9200.26026, now states 6.2.9200.26226Release branch starts at 6.2.9200.0. | Days to revision 122 |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2012 (server core installation) | stated at publication 6.2.9200.26026, now states 6.2.9200.26226Release branch starts at 6.2.9200.0. | Days to revision 122 |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2012 r2 | stated at publication 6.3.9600.23132, now states 6.3.9600.23291Release branch starts at 6.3.9600.0. | Days to revision 122 |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2012 r2 (server core installation) | stated at publication 6.3.9600.23132, now states 6.3.9600.23291Release branch starts at 6.3.9600.0. | Days to revision 122 |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2016 | stated at publication 10.0.14393.9060, now states 10.0.14393.9339Release branch starts at 10.0.14393.0. | Days to revision 122 |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2016 (server core installation) | stated at publication 10.0.14393.9060, now states 10.0.14393.9339Release branch starts at 10.0.14393.0. | Days to revision 122 |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2019 | stated at publication 10.0.17763.8644, now states 10.0.17763.9020Release branch starts at 10.0.17763.0. | Days to revision 122 |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2019 (server core installation) | stated at publication 10.0.17763.8644, now states 10.0.17763.9020Release branch starts at 10.0.17763.0. | Days to revision 122 |
| 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. | Days to revision 122 |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2025 | stated at publication 10.0.26100.32690, now states 10.0.26100.33158Release branch starts at 10.0.26100.0. | Days to revision 122 |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2025 (server core installation) | stated at publication 10.0.26100.32690, now states 10.0.26100.33158Release branch starts at 10.0.26100.0. | Days to revision 122 |
| 2026-08-14 | CVSS base score changed | CVE-2026-65796 | whole record microsoft | stated at publication 5.9, now states 8.1CVSS v3.1 · base scoreMediumHigh | Days to revision 3 |
| Thu 13 Aug 2026· 25 record changes | |||||
| 2026-08-13 | Product added | CVE-2026-65807 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68793 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68794 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68795 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68796 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68797 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68799 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68800 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68801 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68802 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68803 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68804 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68805 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68806 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68807 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68808 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68810 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68811 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68812 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68814 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68815 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68816 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-68817 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-70327 | not named as affected at publication, now names office online server | Days to revision 2 | |
| 2026-08-13 | Product added | CVE-2026-70328 | not named as affected at publication, now names office online server | Days to revision 2 | |
| Tue 11 Aug 2026· 1 record change | |||||
| 2026-08-11 | Product added | CVE-2026-59118 | not named as affected at publication, now names copilot cowork | Days to revision 5 | |
| Mon 3 Aug 2026· 2 record changes | |||||
| 2026-08-03 | CVSS base score changed | CVE-2026-47296 | whole record microsoft | stated at publication 7.8, now states 7.5CVSS v3.1 · base scoreHighHigh | Days to revision 20 |
| 2026-08-03 | CVSS base score changed | CVE-2026-55002 | whole record microsoft | stated at publication 7.8, now states 8.8CVSS v3.1 · base scoreHighHigh | Days to revision 20 |
| Tue 28 Jul 2026· 28 record changes | |||||
| 2026-07-28 | Fix version moved | CVE-2026-45500 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45500 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45500 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45500 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45501 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45501 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45501 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45501 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45502 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45502 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45502 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45502 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45503 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45503 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45503 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45503 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45504 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45504 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45504 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45504 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45583 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45583 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45583 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-45583 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-47631 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-47631 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-47631 | 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. | Days to revision 49 |
| 2026-07-28 | Fix version moved | CVE-2026-47631 | 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. | Days to revision 49 |
| Sun 26 Jul 2026· 2 record changes | |||||
| 2026-07-26 | Product added | CVE-2026-48561 | not named as affected at publication, now names microsoft edge copilot for android | Days to revision 12 | |
| 2026-07-26 | Product added | CVE-2026-48561 | not named as affected at publication, now names microsoft edge copilot for ios | Days to revision 12 | |
| Wed 22 Jul 2026· 8 record changes | |||||
| 2026-07-22 | Fix version moved | CVE-2026-50524 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Days to revision 8 |
| 2026-07-22 | Fix version moved | CVE-2026-50525 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Days to revision 8 |
| 2026-07-22 | Fix version moved | CVE-2026-50526 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Days to revision 8 |
| 2026-07-22 | Fix version moved | CVE-2026-50527 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Days to revision 8 |
| 2026-07-22 | Fix version moved | CVE-2026-50528 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Days to revision 8 |
| 2026-07-22 | Fix version moved | CVE-2026-50648 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Days to revision 8 |
| 2026-07-22 | Fix version moved | CVE-2026-50651 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Days to revision 8 |
| 2026-07-22 | Fix version moved | CVE-2026-50659 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Days to revision 8 |
Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.
Data sources and quality
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 →