Every fix version that moved
| 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. | 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. |
|---|---|---|---|---|
| Wed 2 Sep 2026· 9 record changes | ||||
| 2026-09-02 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 14 Aug 2026· 18 record changes | ||||
| 2026-08-14 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| Tue 28 Jul 2026· 28 record changes | ||||
| 2026-07-28 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| Wed 22 Jul 2026· 11 record changes | ||||
| 2026-07-22 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
| 2026-07-22 | CVE-2026-47300 | 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 | CVE-2026-47302 | 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 | CVE-2026-47303 | 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 |
| Mon 15 Jun 2026· 3 record changes | ||||
| 2026-06-15 | CVE-2026-47287 | microsoftvisual studio code | stated at publication 1.123.1, now states 1.123.2Release branch starts at 1.0.0. | Days to revision 6 |
| 2026-06-15 | CVE-2026-47281 | microsoftvisual studio code | stated at publication 1.123.1, now states 1.123.2Release branch starts at 1.0.0. | Days to revision 6 |
| 2026-06-15 | CVE-2026-47284 | microsoftvisual studio code | stated at publication 1.123.1, now states 1.123.2Release branch starts at 1.0.0. | Days to revision 6 |
| Wed 10 Jun 2026· 3 record changes | ||||
| 2026-06-10 | CVE-2026-40376 | microsoftvisual studio code | stated at publication 1.119.1, now states 1.123.2Release branch starts at 1.0.0. | Days to revision 1 |
| 2026-06-10 | CVE-2026-45482 | microsoftmicrosoft visual studio code copilot chat extension | stated at publication 1.123.1, now states 1.123.2Release branch starts at 0.27.0. | Days to revision 1 |
| 2026-06-10 | CVE-2026-48569 | microsoftvisual studio code | stated at publication 1.119.1, now states 1.123.2Release branch starts at 1.0.0. | Days to revision 1 |
| Tue 9 Jun 2026· 28 record changes | ||||
| 2026-06-09 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
This kind is counted once per record, product and release branch, so one record that moved the boundary on four branches counts four times and the number of records behind these changes is smaller. 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 →