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 or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together. | Vendor or package, 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· 100 changes | |||||
| 2026-06-09 | Added to CISA KEV | CVE-2026-11645 | GoogleChromium V8 CISA KEV | fix due 2026-06-23 | Duration unknown |
| 2026-06-09 | Added to CISA KEV | CVE-2026-7473 | AristaExtensible Operating System CISA KEV | fix due 2026-06-23 | Duration unknown |
| 2026-06-09 | Added to CISA KEV | CVE-2026-20245 | CiscoCatalyst SD-WAN Manager CISA KEV | fix due 2026-06-23 | Duration unknown |
| 2026-06-09 | Ransomware use confirmed | CVE-2026-50751 | Check PointSecurity Gateway CISA KEV | stated at publication Unknown, now states Known | Time to revision 1 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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. | Time to revision 238 days |
| 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. | Time to revision 238 days |
| 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. | Time to revision 238 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 2026-06-09 | Product added | CVE-2026-41100 | not named as affected at publication, now names microsoft excel for android | Time to revision 28 days | |
| 2026-06-09 | Product added | CVE-2026-41100 | not named as affected at publication, now names microsoft loop for android | Time to revision 28 days | |
| 2026-06-09 | Product added | CVE-2026-41100 | not named as affected at publication, now names microsoft onenote for android | Time to revision 28 days | |
| 2026-06-09 | Product added | CVE-2026-41100 | not named as affected at publication, now names microsoft powerpoint for android | Time to revision 28 days | |
| 2026-06-09 | Product added | CVE-2026-41100 | not named as affected at publication, now names microsoft word for android | Time to revision 28 days | |
| 2026-06-09 | Product added | CVE-2026-8863 | certcc | not named as affected at publication, now names oraclelinux(7.2) shim | Time to revision 0 days |
| 2026-06-09 | Product added | CVE-2024-43582 | not named as affected at publication, now names windows 11 version 26h1 | Time to revision 609 days | |
| 2026-06-09 | Product added | CVE-2024-49075 | not named as affected at publication, now names windows 11 version 26h1 | Time to revision 546 days | |
| 2026-06-09 | Product added | CVE-2024-49123 | not named as affected at publication, now names windows 11 version 26h1 | Time to revision 546 days | |
| 2026-06-09 | Product added | CVE-2024-49132 | not named as affected at publication, now names windows 11 version 26h1 | Time to revision 546 days | |
| 2026-06-09 | Product added | CVE-2025-21330 | not named as affected at publication, now names windows 11 version 26h1 | Time to revision 511 days | |
| 2026-06-09 | Product added | CVE-2026-21530 | not named as affected at publication, now names microsoft 365 apps for enterprise | Time to revision 28 days | |
| 2026-06-09 | Product added | CVE-2026-21530 | not named as affected at publication, now names microsoft office 2016 | Time to revision 28 days | |
| 2026-06-09 | Product added | CVE-2026-21530 | not named as affected at publication, now names microsoft office 2019 | Time to revision 28 days | |
| 2026-06-09 | Product added | CVE-2026-21530 | not named as affected at publication, now names microsoft office ltsc 2021 | Time to revision 28 days | |
| 2026-06-09 | Product added | CVE-2026-21530 | not named as affected at publication, now names microsoft office ltsc 2024 | Time to revision 28 days | |
| 2026-06-09 | Product added | CVE-2026-4366 | not named as affected at publication, now names red hat build of keycloak 26.4 | Time to revision 84 days | |
| 2026-06-09 | Product added | CVE-2026-24858 | not named as affected at publication, now names fortinac-f | Time to revision 133 days | |
| 2026-06-09 | Product added | CVE-2025-40936 | not named as affected at publication, now names simcenter femap | Time to revision 204 days | |
| 2026-06-09 | Product added | CVE-2025-66274 | qnap | not named as affected at publication, now names qts | Time to revision 118 days |
| 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 | Time to revision 4 days |
| 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 | Time to revision 348 days |
| 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 | Time to revision 348 days |
| 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 | Time to revision 5 days |
| 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 | Time to revision 158 days |
| 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 | Time to revision 118 days |
| 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 | Time to revision 81 days |
| 2026-06-09 | Record state changed | CVE-2026-26957 | whole record GitHub_M | stated at publication PUBLISHED, now states REJECTED | Time to revision 110 days |
| 2026-06-09published 2022-01-06 | Advisory fix version moved | GHSA-9qj6-4rfq-vm84CVE-2018-25024 | crates.ioactix-web critical | stated at publication 0.7.15, now states 0.7.19 | Duration unknown |
| 2026-06-09published 2022-01-06 | Advisory fix version moved | GHSA-7x36-h62w-vw65CVE-2018-25026 | crates.ioactix-web critical | stated at publication 0.7.15, now states 0.7.19 | Duration unknown |
| 2026-06-09published 2022-01-06 | Advisory fix version moved | GHSA-fgfm-hqjw-3265CVE-2018-25025 | crates.ioactix-web critical | stated at publication 0.7.15, now states 0.7.19 | Duration unknown |
| 2026-06-09published 2021-08-25 | Advisory fix version moved | GHSA-w65j-g6c7-g3m4 | crates.ioactix-web moderate | stated at publication 0.7.15, now states 0.7.19 | Duration unknown |
| 2026-06-09published 2026-06-01 | Package added to advisory | GHSA-q53q-5r4j-5729CVE-2026-47425 | moderate | not named as affected when the advisory was published, now names py-rattler | Time to revision 8 days |
| 2026-06-09published 2026-05-29 | Advisory severity changed | GHSA-j6fm-9rfm-j5hxCVE-2026-41237 | whole advisoryhigh | stated at publication MODERATE, now states HIGHNo CVSS vector was stated in the first observed version. | Time to revision 11 days |
| 2026-06-09published 2022-05-24 | Advisory severity changed | GHSA-4hm9-844j-jmxpCVE-2019-13117 | whole advisorymoderate | stated at publication HIGH, now states MODERATENo CVSS vector was stated in the first observed version. | Time to revision 1,477 days |
| 2026-06-09published 2026-05-12 | Advisory severity changed | GHSA-3636-h3vx-6465CVE-2026-44593 | whole advisoryhigh | stated at publication CRITICAL, now states HIGHNo CVSS vector was stated in the first observed version. | Time to revision 27 days |
Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.
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 →