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 change | |||||
| 2026-09-03 | Product added | CVE-2026-58641 | not named as affected at publication, now names skiasharp | Time to revision 23 days | |
| Wed 2 Sep 2026· 9 changes | |||||
| 2026-09-02 | Fix version moved | CVE-2026-65675 | microsoftmicrosoft visual studio code copilot chat extension | stated at publication 1.132.1, now states 1.135Release branch starts at 0.27.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | Fix version moved | microsoftvisual studio code | stated at publication 1.132.1, now states 1.135Release branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days | |
| 2026-09-02 | same kind of change as the line above | CVE-2026-58650 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-59113 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-47285 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-69320 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-69278 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-69306 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-70335 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-70336 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| Fri 28 Aug 2026· 1 change | |||||
| 2026-08-28 | Product added | CVE-2026-59133 | not named as affected at publication, now names microsoft hpc pack 2019 | Time to revision 17 days | |
| Thu 27 Aug 2026· 1 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 | Time to revision 16 days |
| Thu 20 Aug 2026· 2 changes | |||||
| 2026-08-20 | CVSS base score changed | whole record microsoft | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 37 days | |
| 2026-08-20 | same kind of change as the line above | CVE-2026-54117 | same vendor as the line above | same change as the line above | Time to revision 37 days |
| 2026-08-20 | same kind of change as the line above | CVE-2026-54118 | same vendor as the line above | same change as the line above | Time to revision 37 days |
| Sun 16 Aug 2026· 1 change | |||||
| 2026-08-16 | Product added | CVE-2026-59124 | not named as affected at publication, now names microsoft hpc pack 2019 | Time to revision 5 days | |
| Fri 14 Aug 2026· 19 changes | |||||
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoft3 products | stated at publication 10.0.14393.9060, now states 10.0.14393.9339Release branch starts at 10.0.14393.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoft3 products | stated at publication 10.0.17763.8644, now states 10.0.17763.9020Release branch starts at 10.0.17763.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 10 version 21h2 | stated at publication 10.0.19044.7184, now states 10.0.19044.7548Release branch starts at 10.0.19044.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7184, now states 10.0.19045.7548Release branch starts at 10.0.19045.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 11 version 23h2 | stated at publication 10.0.22631.6936, now states 10.0.22631.7376Release branch starts at 10.0.22631.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 11 version 25h2 | stated at publication 10.0.26200.8246, now states 10.0.26200.8875Release branch starts at 10.0.26200.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.1836, now states 10.0.28000.2525Release branch starts at 10.0.28000.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoft2 products | stated at publication 6.2.9200.26026, now states 6.2.9200.26226Release branch starts at 6.2.9200.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoft2 products | stated at publication 6.3.9600.23132, now states 6.3.9600.23291Release branch starts at 6.3.9600.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoftwindows server 2022 | stated at publication 10.0.20348.5020, now states 10.0.20348.5386Release branch starts at 10.0.20348.0. | Time to revision 122 days |
| 2026-08-14 | Fix version moved | CVE-2026-32202 | microsoft2 products | stated at publication 10.0.26100.32690, now states 10.0.26100.33158Release branch starts at 10.0.26100.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0. | Time to revision 122 days |
| 2026-08-14 | same kind of change as the line above | CVE-2026-32202 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0. | Time to revision 122 days |
| 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 | Time to revision 3 days |
| Thu 13 Aug 2026· 25 changes | |||||
| 2026-08-13 | Product added | not named as affected at publication, now names office online server | Time to revision 2 days | ||
| 2026-08-13 | same kind of change as the line above | CVE-2026-65807 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68793 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68794 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68795 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68796 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68797 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68799 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-68800 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 17 more rows in this change are not listed here. Open all 25 rows → | |||||
| Tue 11 Aug 2026· 1 change | |||||
| 2026-08-11 | Product added | CVE-2026-59118 | not named as affected at publication, now names copilot cowork | Time to revision 5 days | |
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
What this page cannot see
Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
The units, the refusals, the cut-offs and every source, in full →
Paste your closed CVE tickets and see which of these changes hit them →