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. |
|---|---|---|---|---|---|
| Fri 13 Mar 2026· 11 record changes | |||||
| 2026-03-13 | Product added | CVE-2026-26111 | not named as affected at publication, now names windows 10 version 22h2 | Days to revision 3 | |
| 2026-03-13 | Product added | CVE-2026-26111 | not named as affected at publication, now names windows 11 version 22h3 | Days to revision 3 | |
| 2026-03-13 | Product added | CVE-2026-26111 | not named as affected at publication, now names windows 11 version 23h2 | Days to revision 3 | |
| 2026-03-13 | Product added | CVE-2026-26111 | not named as affected at publication, now names windows 11 version 24h2 | Days to revision 3 | |
| 2026-03-13 | Product added | CVE-2026-26111 | not named as affected at publication, now names windows 11 version 25h2 | Days to revision 3 | |
| 2026-03-13 | Product added | CVE-2026-26111 | not named as affected at publication, now names windows 11 version 26h1 | Days to revision 3 | |
| 2026-03-13 | Product added | CVE-2026-20846 | not named as affected at publication, now names microsoft office for android | Days to revision 31 | |
| 2026-03-13 | Product added | CVE-2026-21256 | not named as affected at publication, now names microsoft visual studio 2026 version 18.3 | Days to revision 31 | |
| 2026-03-13 | Product added | CVE-2026-21257 | not named as affected at publication, now names microsoft visual studio 2026 version 18.3 | Days to revision 31 | |
| 2026-03-13 | CVSS base score changed | CVE-2026-25172 | whole record microsoft | stated at publication 8.8, now states 8.0CVSS v3.1 · base scoreHighHigh | Days to revision 3 |
| 2026-03-13 | CVSS base score changed | CVE-2026-26111 | whole record microsoft | stated at publication 8.8, now states 8.0CVSS v3.1 · base scoreHighHigh | Days to revision 3 |
| Fri 27 Feb 2026· 2 record changes | |||||
| 2026-02-27 | Product added | CVE-2026-21523 | not named as affected at publication, now names microsoft visual studio code copilot chat extension | Days to revision 17 | |
| 2026-02-27 | Product added | CVE-2026-21518 | not named as affected at publication, now names microsoft visual studio code copilot chat extension | Days to revision 17 | |
| Mon 23 Feb 2026· 1 record change | |||||
| 2026-02-23 | CVSS base score changed | CVE-2026-21518 | whole record microsoft | stated at publication 6.5, now states 8.8CVSS v3.1 · base scoreMediumHigh | Days to revision 13 |
| Fri 13 Feb 2026· 4 record changes | |||||
| 2026-02-13 | Product added | CVE-2025-21264 | not named as affected at publication, now names microsoft visual studio code copilot chat extension | Days to revision 276 | |
| 2026-02-13 | Product added | CVE-2025-27488 | not named as affected at publication, now names windows hlk, version 1809 | Days to revision 276 | |
| 2026-02-13 | Product added | CVE-2025-47733 | not named as affected at publication, now names microsoft power pages | Days to revision 281 | |
| 2026-02-13 | CVSS base score changed | CVE-2025-59213 | whole record microsoft | stated at publication 8.4, now states 8.8CVSS v3.1 · base scoreHighHigh | Days to revision 122 |
| Thu 12 Feb 2026· 1 record change | |||||
| 2026-02-12 | CVSS base score changed | CVE-2026-20841 | whole record microsoft | stated at publication 8.8, now states 7.8CVSS v3.1 · base scoreHighHigh | Days to revision 2 |
| Wed 11 Feb 2026· 1 record change | |||||
| 2026-02-11 | CVSS base score changed | CVE-2026-21517 | whole record microsoft | stated at publication 7.0, now states 4.7CVSS v3.1 · base scoreHighMedium | Days to revision 0 |
| Fri 12 Dec 2025· 1 record change | |||||
| 2025-12-12 | CVSS base score changed | CVE-2025-62468 | whole record microsoft | stated at publication 4.4, now states 5.5CVSS v3.1 · base scoreMediumMedium | Days to revision 3 |
| Tue 9 Dec 2025· 4 record changes | |||||
| 2025-12-09 | Fix version moved | 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. | Days to revision 28 |
| 2025-12-09 | Product added | CVE-2025-60710 | not named as affected at publication, now names windows 11 version 24h2 | Days to revision 28 | |
| 2025-12-09 | Product added | CVE-2025-60710 | not named as affected at publication, now names windows server 2025 | Days to revision 28 | |
| 2025-12-09 | Product added | CVE-2025-60710 | not named as affected at publication, now names windows server 2025 (server core installation) | Days to revision 28 | |
| Tue 25 Nov 2025· 1 record change | |||||
| 2025-11-25 | CVSS base score changed | CVE-2025-64660 | whole record microsoft | stated at publication 5.7, now states 8.0CVSS v3.1 · base scoreMediumHigh | Days to revision 5 |
| Sat 22 Nov 2025· 3 record changes | |||||
| 2025-11-22 | CVSS base score changed | CVE-2025-59252 | whole record microsoft | stated at publication 6.5, now states 9.3CVSS v3.1 · base scoreMediumCritical | Days to revision 43 |
| 2025-11-22 | CVSS base score changed | CVE-2025-59272 | whole record microsoft | stated at publication 6.5, now states 9.3CVSS v3.1 · base scoreMediumCritical | Days to revision 43 |
| 2025-11-22 | CVSS base score changed | CVE-2025-59286 | whole record microsoft | stated at publication 6.5, now states 9.3CVSS v3.1 · base scoreMediumCritical | Days to revision 43 |
| Wed 12 Nov 2025· 6 record changes | |||||
| 2025-11-12 | Product added | CVE-2025-60726 | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Days to revision 0 | |
| 2025-11-12 | Product added | CVE-2025-60726 | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Days to revision 0 | |
| 2025-11-12 | Product added | CVE-2025-60727 | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Days to revision 0 | |
| 2025-11-12 | Product added | CVE-2025-60727 | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Days to revision 0 | |
| 2025-11-12 | Product added | CVE-2025-62203 | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Days to revision 0 | |
| 2025-11-12 | Product added | CVE-2025-62203 | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Days to revision 0 | |
| Fri 31 Oct 2025· 1 record change | |||||
| 2025-10-31 | CVSS base score changed | CVE-2025-59503 | whole record microsoft | stated at publication 9.9, now states 10.0CVSS v3.1 · base scoreCriticalCritical | Days to revision 8 |
| Thu 23 Oct 2025· 1 record change | |||||
| 2025-10-23 | CVSS base score changed | CVE-2025-55321 | whole record microsoft | stated at publication 8.7, now states 9.3CVSS v3.1 · base scoreHighCritical | Days to revision 14 |
| Fri 17 Oct 2025· 1 record change | |||||
| 2025-10-17 | CVSS base score changed | CVE-2025-55320 | whole record microsoft | stated at publication 6.7, now states 6.8CVSS v3.1 · base scoreMediumMedium | Days to revision 3 |
| Wed 15 Oct 2025· 3 record changes | |||||
| 2025-10-15 | Fix version moved | 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. | Days to revision 1 |
| 2025-10-15 | Product added | CVE-2025-50173 | not named as affected at publication, now names multimedia redirection installer | Days to revision 64 | |
| 2025-10-15 | CVSS base score changed | CVE-2025-53132 | whole record microsoft | stated at publication 8.0, now states 7.8CVSS v3.1 · base scoreHighHigh | Days to revision 64 |
| Thu 18 Sep 2025· 1 record change | |||||
| 2025-09-18 | CVSS base score changed | CVE-2025-55241 | whole record microsoft | stated at publication 9.0, now states 10.0CVSS v3.1 · base scoreCriticalCritical | Days to revision 14 |
| Wed 17 Sep 2025· 1 record change | |||||
| 2025-09-17 | CVSS base score changed | CVE-2025-50154 | whole record microsoft | stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium | Days to revision 36 |
| Thu 11 Sep 2025· 2 record changes | |||||
| 2025-09-11 | Product added | CVE-2025-49734 | not named as affected at publication, now names powershell 7.4 | Days to revision 2 | |
| 2025-09-11 | Product added | CVE-2025-49734 | not named as affected at publication, now names powershell 7.5 | Days to revision 2 | |
| Tue 9 Sep 2025· 16 record changes | |||||
| 2025-09-09 | Fix version moved | CVE-2025-21293 | microsoftwindows 11 version 24h2 | stated at publication 10.0.26100.2894, now states 10.0.26100.6584Release branch starts at 10.0.26100.0. | Days to revision 238 |
| 2025-09-09 | Fix version moved | CVE-2025-21293 | microsoftwindows server 2025 | stated at publication 10.0.26100.2894, now states 10.0.26100.6584Release branch starts at 10.0.26100.0. | Days to revision 238 |
| 2025-09-09 | Fix version moved | CVE-2025-21293 | microsoftwindows server 2025 (server core installation) | stated at publication 10.0.26100.2894, now states 10.0.26100.6584Release branch starts at 10.0.26100.0. | Days to revision 238 |
| 2025-09-09 | Fix version moved | CVE-2025-48807 | microsoftwindows 10 version 1607 | stated at publication 10.0.14393.8246, now states 10.0.14393.8422Release branch starts at 10.0.14393.0. | Days to revision 28 |
| 2025-09-09 | Fix version moved | CVE-2025-48807 | microsoftwindows 10 version 1809 | stated at publication 10.0.17763.7558, now states 10.0.17763.7792Release branch starts at 10.0.17763.0. | Days to revision 28 |
| 2025-09-09 | Fix version moved | 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. | Days to revision 28 |
| 2025-09-09 | Fix version moved | 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. | Days to revision 28 |
| 2025-09-09 | Fix version moved | CVE-2025-48807 | microsoftwindows 11 version 24h2 | stated at publication 10.0.26100.4652, now states 10.0.26100.6584Release branch starts at 10.0.26100.0. | Days to revision 28 |
| 2025-09-09 | Fix version moved | CVE-2025-48807 | microsoftwindows server 2016 | stated at publication 10.0.14393.8246, now states 10.0.14393.8422Release branch starts at 10.0.14393.0. | Days to revision 28 |
| 2025-09-09 | Fix version moved | CVE-2025-48807 | microsoftwindows server 2016 (server core installation) | stated at publication 10.0.14393.8246, now states 10.0.14393.8422Release branch starts at 10.0.14393.0. | Days to revision 28 |
| 2025-09-09 | Fix version moved | CVE-2025-48807 | microsoftwindows server 2019 | stated at publication 10.0.17763.7558, now states 10.0.17763.7792Release branch starts at 10.0.17763.0. | Days to revision 28 |
| 2025-09-09 | Fix version moved | CVE-2025-48807 | microsoftwindows server 2019 (server core installation) | stated at publication 10.0.17763.7558, now states 10.0.17763.7792Release branch starts at 10.0.17763.0. | Days to revision 28 |
| 2025-09-09 | Fix version moved | 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. | Days to revision 28 |
| 2025-09-09 | Fix version moved | 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. | Days to revision 28 |
| 2025-09-09 | Fix version moved | CVE-2025-48807 | microsoftwindows server 2025 | stated at publication 10.0.26100.4652, now states 10.0.26100.6584Release branch starts at 10.0.26100.0. | Days to revision 28 |
| 2025-09-09 | Fix version moved | CVE-2025-48807 | microsoftwindows server 2025 (server core installation) | stated at publication 10.0.26100.4652, now states 10.0.26100.6584Release branch starts at 10.0.26100.0. | Days to revision 28 |
| Thu 21 Aug 2025· 1 record change | |||||
| 2025-08-21 | CVSS base score changed | CVE-2025-48807 | whole record microsoft | stated at publication 7.5, now states 6.7CVSS v3.1 · base scoreHighMedium | Days to revision 9 |
| Fri 15 Aug 2025· 6 record changes | |||||
| 2025-08-15 | Product added | CVE-2025-50171 | not named as affected at publication, now names windows 10 version 21h2 | Days to revision 3 | |
| 2025-08-15 | Product added | CVE-2025-50171 | not named as affected at publication, now names windows 10 version 22h2 | Days to revision 3 | |
| 2025-08-15 | Product added | CVE-2025-50171 | not named as affected at publication, now names windows 11 version 22h2 | Days to revision 3 | |
| 2025-08-15 | Product added | CVE-2025-50171 | not named as affected at publication, now names windows 11 version 22h3 | Days to revision 3 | |
| 2025-08-15 | Product added | CVE-2025-50171 | not named as affected at publication, now names windows 11 version 23h2 | Days to revision 3 | |
| 2025-08-15 | Product added | CVE-2025-50171 | not named as affected at publication, now names windows 11 version 24h2 | Days to revision 3 | |
| Tue 12 Aug 2025· 1 record change | |||||
| 2025-08-12 | Fix version moved | 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 | Days to revision 0 |
| Tue 22 Jul 2025· 2 record changes | |||||
| 2025-07-22 | CVSS base score changed | CVE-2025-49706 | whole record microsoft | stated at publication 6.3, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2025-07-21; this value first seen 2025-07-22. | Days to revision 13 |
| 2025-07-22 | CVSS base score changed | CVE-2025-53771 | whole record microsoft | stated at publication 6.3, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2025-07-21; this value first seen 2025-07-22. | Days to revision 1 |
| Tue 15 Jul 2025· 1 record change | |||||
| 2025-07-15 | CVSS base score changed | CVE-2025-49716 | whole record microsoft | stated at publication 5.9, now states 7.5CVSS v3.1 · base scoreMediumHigh | Days to revision 7 |
| Fri 11 Jul 2025· 2 record changes | |||||
| 2025-07-11 | Fix version moved | 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. | Days to revision 31 |
| 2025-07-11 | CVSS base score changed | CVE-2025-49670 | whole record microsoft | stated at publication 8.8, now states 6.5CVSS v3.1 · base scoreHighMedium | Days to revision 3 |
| Tue 8 Jul 2025· 5 record changes | |||||
| 2025-07-08 | Fix version moved | 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. | Days to revision 238 |
| 2025-07-08 | Fix version moved | 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. | Days to revision 238 |
| 2025-07-08 | Product added | CVE-2025-30399 | not named as affected at publication, now names powershell 7.4 | Days to revision 26 | |
| 2025-07-08 | Product added | CVE-2025-30399 | not named as affected at publication, now names powershell 7.5 | Days to revision 26 | |
| 2025-07-08 | CVSS base score changed | CVE-2025-49691 | whole record microsoft | stated at publication 8.8, now states 8.0CVSS v3.1 · base scoreHighHigh | Days to revision 0 |
| Mon 16 Jun 2025· 1 record change | |||||
| 2025-06-16 | Product added | CVE-2024-38179 | not named as affected at publication, now names azure stack os hci | Days to revision 250 | |
| Thu 12 Jun 2025· 1 record change | |||||
| 2025-06-12 | CVSS base score changed | CVE-2025-47977 | whole record microsoft | stated at publication 7.6, now states 8.2CVSS v3.1 · base scoreHighHigh | Days to revision 2 |
| Thu 22 May 2025· 1 record change | |||||
| 2025-05-22 | Fix version moved | 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. | Days to revision 9 |
| Thu 15 May 2025· 18 record changes | |||||
| 2025-05-15 | Product added | CVE-2025-29977 | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-29977 | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-29979 | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-29979 | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30375 | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30375 | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30379 | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30379 | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30381 | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30381 | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30383 | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30383 | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30393 | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30393 | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30376 | not named as affected at publication, now names microsoft office ltsc for mac 2021 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-30376 | not named as affected at publication, now names microsoft office ltsc for mac 2024 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-32709 | not named as affected at publication, now names windows server 2008 r2 service pack 1 | Days to revision 2 | |
| 2025-05-15 | Product added | CVE-2025-32709 | not named as affected at publication, now names windows server 2008 r2 service pack 1 (server core installation) | Days to revision 2 | |
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 →