Every change, newest first
Showing changes seen on 2026-06-09. Every day
| 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. |
|---|---|---|---|---|---|
| Tue 9 Jun 2026· 88 record changes | |||||
| 2026-06-09 | Fix version moved | CVE-2026-21530 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-33834 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-33839 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-33841 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34329 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34330 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34331 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34333 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34342 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34343 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34344 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34345 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34347 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34351 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-35415 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-35416 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-35417 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-35418 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-35421 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-35422 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-35423 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-35424 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40377 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40380 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40399 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40406 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40407 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40408 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40410 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40414 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40415 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-41088 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-32161 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-32170 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-42825 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-33835 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-33837 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-33838 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34334 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34336 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34337 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34338 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34339 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34340 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-34341 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40382 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40397 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-32209 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40398 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40401 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40403 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-40413 | 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 | Days to revision 28 |
| 2026-06-09 | Fix version moved | CVE-2026-41097 | 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 | Days to revision 28 |
| 2026-06-09 | Affected range extended | CVE-2025-31514 | fortinetfortios | stated at publication 7.2.12, now states 7.2.13Release branch starts at 7.2.0. | Days to revision 238 |
| 2026-06-09 | Affected range extended | CVE-2025-31514 | fortinetfortios | stated at publication 7.4.9, now states 7.4.11Release branch starts at 7.4.0. | Days to revision 238 |
| 2026-06-09 | Affected range extended | CVE-2025-31514 | fortinetfortiproxy | stated at publication 7.2.15, now states 7.2.16Release branch starts at 7.2.0. | Days to revision 238 |
| 2026-06-09 | Affected range extended | CVE-2025-31514 | fortinetfortios | stated at publication 7.0.17, now states 7.0.19Release branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-06-09. | Days to revision 92 |
| 2026-06-09 | Affected range extended | CVE-2025-31514 | fortinetfortiproxy | stated at publication 7.4.11, now states 7.4.13Release branch starts at 7.4.0.Original value first replaced 2026-01-14; this value first seen 2026-06-09. | Days to revision 92 |
| 2026-06-09 | Affected range extended | CVE-2025-31514 | fortinetfortiproxy | stated at publication 7.0.21, now states 7.0.23Release branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-06-09. | Days to revision 92 |
| 2026-06-09 | Product added | CVE-2026-41100 | not named as affected at publication, now names microsoft excel for android | Days to revision 28 | |
| 2026-06-09 | Product added | CVE-2026-41100 | not named as affected at publication, now names microsoft loop for android | Days to revision 28 | |
| 2026-06-09 | Product added | CVE-2026-41100 | not named as affected at publication, now names microsoft onenote for android | Days to revision 28 | |
| 2026-06-09 | Product added | CVE-2026-41100 | not named as affected at publication, now names microsoft powerpoint for android | Days to revision 28 | |
| 2026-06-09 | Product added | CVE-2026-41100 | not named as affected at publication, now names microsoft word for android | Days to revision 28 | |
| 2026-06-09 | Product added | CVE-2026-8863 | certcc | not named as affected at publication, now names oraclelinux(7.2) shim | Days to revision 0 |
| 2026-06-09 | Product added | CVE-2024-43582 | not named as affected at publication, now names windows 11 version 26h1 | Days to revision 609 | |
| 2026-06-09 | Product added | CVE-2024-49075 | not named as affected at publication, now names windows 11 version 26h1 | Days to revision 546 | |
| 2026-06-09 | Product added | CVE-2024-49123 | not named as affected at publication, now names windows 11 version 26h1 | Days to revision 546 | |
| 2026-06-09 | Product added | CVE-2024-49132 | not named as affected at publication, now names windows 11 version 26h1 | Days to revision 546 | |
| 2026-06-09 | Product added | CVE-2025-21330 | not named as affected at publication, now names windows 11 version 26h1 | Days to revision 511 | |
| 2026-06-09 | Product added | CVE-2026-21530 | not named as affected at publication, now names microsoft 365 apps for enterprise | Days to revision 28 | |
| 2026-06-09 | Product added | CVE-2026-21530 | not named as affected at publication, now names microsoft office 2016 | Days to revision 28 | |
| 2026-06-09 | Product added | CVE-2026-21530 | not named as affected at publication, now names microsoft office 2019 | Days to revision 28 | |
| 2026-06-09 | Product added | CVE-2026-21530 | not named as affected at publication, now names microsoft office ltsc 2021 | Days to revision 28 | |
| 2026-06-09 | Product added | CVE-2026-21530 | not named as affected at publication, now names microsoft office ltsc 2024 | Days to revision 28 | |
| 2026-06-09 | Product added | CVE-2026-4366 | not named as affected at publication, now names red hat build of keycloak 26.4 | Days to revision 84 | |
| 2026-06-09 | Product added | CVE-2026-24858 | not named as affected at publication, now names fortinac-f | Days to revision 133 | |
| 2026-06-09 | Product added | CVE-2025-40936 | not named as affected at publication, now names simcenter femap | Days to revision 204 | |
| 2026-06-09 | Product added | CVE-2025-66274 | qnap | not named as affected at publication, now names qts | Days to revision 118 |
| 2026-06-09 | CVSS base score changed | CVE-2026-11429 | whole record Altium | stated at publication 9.4, now states 10.0CVSS v4.0 · base scoreCriticalCritical | Days to revision 4 |
| 2026-06-09 | CVSS base score changed | CVE-2025-52903 | whole record GitHub_M | stated at publication 8.1, now states 8.0CVSS v3.1 · base scoreHighHigh | Days to revision 348 |
| 2026-06-09 | CVSS base score changed | CVE-2025-52904 | whole record GitHub_M | stated at publication 8.1, now states 8.0CVSS v3.1 · base scoreHighHigh | Days to revision 348 |
| 2026-06-09 | CVSS base score changed | CVE-2026-10840 | whole record redhat | stated at publication 9.6, now states 7.1CVSS v3.1 · base scoreCriticalHigh | Days to revision 5 |
| 2026-06-09 | CVSS base score changed | CVE-2025-59381 | whole record qnap | stated at publication 4.6, now states 6.9CVSS v4.0 · base scoreMediumMedium | Days to revision 158 |
| 2026-06-09 | CVSS base score changed | CVE-2025-66274 | whole record qnap | stated at publication 1.2, now states 5.1CVSS v4.0 · base scoreLowMedium | Days to revision 118 |
| 2026-06-09 | CVSS base score changed | CVE-2026-22895 | whole record qnap | stated at publication 2.2, now states 6.2CVSS v4.0 · base scoreLowMedium | Days to revision 81 |
| 2026-06-09 | Record state changed | CVE-2026-26957 | whole record GitHub_M | stated at publication PUBLISHED, now states REJECTED | Days to revision 110 |
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 →