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 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. | Time to revision 17 days |
| 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. | Time to revision 17 days |
| 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. | Time to revision 17 days |
| 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. | Time to revision 17 days |
| 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. | Time to revision 17 days |
| 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. | Time to revision 17 days |
| 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. | Time to revision 17 days |
| 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. | Time to revision 17 days |
| 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. | Time to revision 17 days |
| Fri 21 Aug 2026· 1 change | ||||
| 2026-08-21 | CVE-2026-18952 | githubopensearch AMZN | stated at publication 3.5.0, now states 3.7.0Release branch starts at 2.15.0. | Time to revision 9 days |
| Thu 20 Aug 2026· 1 change | ||||
| 2026-08-20 | CVE-2026-17561 | TR-CERT | stated at publication 6.4.108, now states 6.4.115Release branch starts at 0. | Time to revision 20 days |
| Fri 14 Aug 2026· 18 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| 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. | Time to revision 122 days |
| Tue 11 Aug 2026· 2 changes | ||||
| 2026-08-11 | CVE-2026-41472 | usmannasircyberpanel VulnCheck | stated at publication 2.4.4, now states 2.4.5Release branch starts at 0. | Time to revision 109 days |
| 2026-08-11 | CVE-2026-41473 | usmannasircyberpanel VulnCheck | stated at publication 2.4.4, now states 2.4.5Release branch starts at 0. | Time to revision 109 days |
| Sat 8 Aug 2026· 1 change | ||||
| 2026-08-08 | CVE-2025-4106 | watchguardfireware os | stated at publication 12.11.2, now states 12.11.3Release branch starts at 12.0. | Time to revision 287 days |
| Fri 7 Aug 2026· 4 changes | ||||
| 2026-08-07 | CVE-2026-68480 | linuxlinux | stated at publication 5.10.263, now states 5.10.264Release branch starts at 5.10.*.same day | Time to revision 1 days |
| 2026-08-07 | CVE-2026-68480 | linuxlinux | stated at publication 5.15.214, now states 5.15.215Release branch starts at 5.15.*.same day | Time to revision 1 days |
| 2026-08-07 | CVE-2026-68480 | linuxlinux | stated at publication 6.1.181, now states 6.1.182Release branch starts at 6.1.*.same day | Time to revision 1 days |
| 2026-08-07 | CVE-2026-68480 | linuxlinux | stated at publication 6.6.149, now states 6.6.150Release branch starts at 6.6.*.same day | Time to revision 1 days |
| Tue 28 Jul 2026· 28 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| 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. | Time to revision 49 days |
| Fri 24 Jul 2026· 1 change | ||||
| 2026-07-24 | CVE-2026-8661 | rapid7insightconnect markdown plugin | stated at publication 4.0.0, now states 4.0.2Release branch starts at 4.0.0. | Time to revision 28 days |
| Wed 22 Jul 2026· 11 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. | Time to revision 8 days |
| 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. | Time to revision 8 days |
| 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. | Time to revision 8 days |
| 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. | Time to revision 8 days |
| 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. | Time to revision 8 days |
| 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. | Time to revision 8 days |
| 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. | Time to revision 8 days |
| 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. | Time to revision 8 days |
| 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. | Time to revision 8 days |
| 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. | Time to revision 8 days |
| 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. | Time to revision 8 days |
| Tue 21 Jul 2026· 1 change | ||||
| 2026-07-21 | CVE-2026-64824 | home-assistanthome assistant core VulnCheck | stated at publication 2026.6.0, now states 2026.7.0Release branch starts at 0.same day | Time to revision 0 days |
| Wed 1 Jul 2026· 1 change | ||||
| 2026-07-01 | CVE-2026-13006 | qos.ch sarllogback-core NCSC.ch | stated at publication 1.5.35, now states 1.5.37Release branch starts at 1.5.35.Original value first replaced 2026-06-24; this value first seen 2026-07-01.same day | Time to revision 0 days |
| Mon 29 Jun 2026· 1 change | ||||
| 2026-06-29 | CVE-2026-2587 | eclipse foundationeclipse glassfish eclipse | stated at publication 7.1.0, now states 7.1.1Release branch starts at 0.Original value first replaced 2026-05-20; this value first seen 2026-06-29.same day | Time to revision 1 days |
| Thu 25 Jun 2026· 1 change | ||||
| 2026-06-25 | CVE-2026-33813 | golang.org/x/imagegolang.org/x/image/webp Go | stated at publication 0.39.0, now states 0.42.0Release branch starts at 0. | Time to revision 65 days |
| Tue 23 Jun 2026· 2 changes | ||||
| 2026-06-23 | CVE-2026-56784 | openremoteopenremote VulnCheck | stated at publication 1.24.2, now states 1.25.0Release branch starts at 0.same day | Time to revision 0 days |
| 2026-06-23 | CVE-2026-41715 | springreactor netty vmware | stated at publication 1.3.6, now states 1.3.15.1Release branch starts at 1.3.0. | Time to revision 15 days |
| Fri 19 Jun 2026· 4 changes | ||||
| 2026-06-19 | CVE-2026-43064 | linuxlinux | stated at publication 6.1.168, now states 6.1.176Release branch starts at 6.1.*.Original value first replaced 2026-06-01; this value first seen 2026-06-19. | Time to revision 27 days |
| 2026-06-19 | CVE-2026-45852 | linuxlinux | stated at publication 5.10.252, now states 5.10.259Release branch starts at 5.10.*. | Time to revision 23 days |
| 2026-06-19 | CVE-2026-45852 | linuxlinux | stated at publication 5.15.202, now states 5.15.210Release branch starts at 5.15.*. | Time to revision 23 days |
| 2026-06-19 | CVE-2026-45852 | linuxlinux | stated at publication 6.1.165, now states 6.1.176Release branch starts at 6.1.*. | Time to revision 23 days |
| Wed 17 Jun 2026· 2 changes | ||||
| 2026-06-17 | CVE-2026-26236 | qnap systems inc.qumagie qnap | stated at publication 2.9.0, now states 2.9.1Release branch starts at 2.9.0. | Time to revision 8 days |
| 2026-06-17 | CVE-2026-26237 | qnap systems inc.qumagie qnap | stated at publication 2.9.0, now states 2.9.1Release branch starts at 2.9.0. | Time to revision 7 days |
| Mon 15 Jun 2026· 3 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. | Time to revision 6 days |
| 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. | Time to revision 6 days |
| 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. | Time to revision 6 days |
| Wed 10 Jun 2026· 3 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. | Time to revision 1 days |
| 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. | Time to revision 1 days |
| 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. | Time to revision 1 days |
| Tue 9 Jun 2026· 6 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
| 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 | Time to revision 28 days |
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller.
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 →