| CVE-2021-21017US | medium6.8OT critical | 86.3% (100th) | KEV | ✗no fix | 2021-02-11 | ≤ 2017.011.30190 Classic 2017 |
| CVE-2020-9715US | high7.8OT critical | 33.5% (98th) | KEV | ✗no fix | 2020-08-19 | ≤ 2017.011.30175 Classic 2017 |
| CVE-2021-28550US | high8.8OT critical | 51.9% (99th) | KEV | ✗no fix | 2021-09-02 | ≤ 2017.011.30196 Classic 2017 |
| CVE-2018-4990US | high8.8OT critical | 35.9% (98th) | KEV | ✗no fix | 2018-07-09 | ≤ 2017.011.30079 Classic 2017 |
| CVE-2019-16451US | critical9.8 | 34.7% (98th) | Exploit | ✗no fix | 2019-12-19 | ≤ 2017.011.30156 Classic 2017 |
| CVE-2019-8196US | critical9.8 | 22.9% (98th) | Exploit | ✗no fix | 2019-10-17 | ≤ 2017.011.30150 Classic 2017 |
| CVE-2019-8195US | critical9.8 | 22.9% (98th) | Exploit | ✗no fix | 2019-10-17 | ≤ 2017.011.30148 Classic 2017 |
| CVE-2019-8197US | critical9.8 | 16.8% (97th) | Exploit | ✗no fix | 2019-10-17 | ≤ 2017.011.30148 Classic 2017 |
| CVE-2019-8045US | critical9.8 | 16.0% (97th) | Exploit | ✗no fix | 2019-08-20 | ≤ 2017.011.30144 Classic 2017 |
| CVE-2021-21042US | medium6.5 | 14.7% (97th) | Exploit | ✗no fix | 2021-02-11 | ≤ 2017.011.30190 Classic 2017 |
| CVE-2019-8044US | critical9.8 | 14.5% (97th) | Exploit | ✗no fix | 2019-08-20 | ≤ 2017.011.30144 Classic 2017 |
| CVE-2019-8043US | high7.5 | 13.4% (96th) | Exploit | ✗no fix | 2019-08-20 | ≤ 2017.011.30144 Classic 2017 |
| CVE-2021-39863US | medium6.8 | 13.2% (96th) | Exploit | ✗no fix | 2021-09-29 | ≤ 2017.011.30199 Classic 2017 |
| CVE-2021-21086US | high7.8 | 4.71% (92nd) | Exploit | ✗no fix | 2021-09-02 | ≤ 2017.011.30196 Classic 2017 |
| CVE-2019-7069US | high8.8 | 4.51% (91st) | Exploit | ✗no fix | 2019-05-24 | ≤ 2017.011.30120 Classic 2017 |
| CVE-2021-45067US | medium5.5 | 3.56% (89th) | Exploit | ✗no fix | 2022-01-14 | ≤ 17.011.30207 Classic 2017 |
| CVE-2021-39843US | medium6.8 | 76.7% (100th) | — | ✗no fix | 2021-09-29 | ≤ 2017.011.30202 Classic 2017 |
| CVE-2021-39836US | high7.8 | 69.5% (99th) | — | ✗no fix | 2021-09-29 | ≤ 2017.011.30202 Classic 2017 |
| CVE-2021-28560US | medium6.8 | 66.9% (99th) | — | ✗no fix | 2021-09-02 | ≤ 2017.011.30196 Classic 2017 |
| CVE-2021-28639US | high9.3 | 66.1% (99th) | — | ✗no fix | 2021-08-20 | ≤ 2017.011.30199 Classic 2017 |
| CVE-2021-39839US | medium6.8 | 65.2% (99th) | — | ✗no fix | 2021-09-29 | ≤ 2017.011.30202 Classic 2017 |
| CVE-2021-39838US | medium6.8 | 65.2% (99th) | — | ✗no fix | 2021-09-29 | ≤ 2017.011.30202 Classic 2017 |
| CVE-2021-39837US | medium6.8 | 65.2% (99th) | — | ✗no fix | 2021-09-29 | ≤ 2017.011.30202 Classic 2017 |
| CVE-2021-39840US | medium6.8 | 60.8% (99th) | — | ✗no fix | 2021-09-29 | ≤ 2017.011.30202 Classic 2017 |
| CVE-2021-44703US | high7.8 | 57.3% (99th) | — | ✗no fix | 2022-01-14 | ≤ 17.011.30207 Classic 2017 |
| CVE-2019-7111US | high8.8 | 55.7% (99th) | — | ✗no fix | 2019-05-23 | ≤ 2017.011.30127 Classic 2017 |
| CVE-2021-40728US | medium6.8 | 54.6% (99th) | — | ✗no fix | 2021-10-15 | ≤ 17.011.30204 Classic 2017 |
| CVE-2021-28640US | medium6.0 | 53.4% (99th) | — | ✗no fix | 2021-08-20 | ≤ 2017.011.30199 Classic 2017 |
| CVE-2020-24435US | high7.8 | 52.7% (99th) | — | ✗no fix | 2020-11-05 | ≤ 2017.011.30180 Classic 2017 |
| CVE-2021-28635US | high9.3 | 51.2% (99th) | — | ✗no fix | 2021-08-20 | ≤ 2017.011.30199 Classic 2017 |
| CVE-2020-24437US | high7.8 | 46.5% (99th) | — | ✗no fix | 2020-11-05 | ≤ 2017.011.30180 Classic 2017 |
| CVE-2021-44708US | high7.8 | 38.2% (99th) | — | ✗no fix | 2022-01-14 | ≤ 17.011.30207 Classic 2017 |
| CVE-2018-4985US | high7.5 | 36.4% (98th) | — | ✗no fix | 2018-07-09 | ≤ 2017.011.30079 Classic 2017 |
| CVE-2018-12848US | critical9.8 | 34.7% (98th) | — | ✗no fix | 2018-09-25 | ≤ 2017.011.30099 Classic 2017 |
| CVE-2018-12850US | high7.5 | 33.6% (98th) | — | ✗no fix | 2018-09-25 | ≤ 2017.011.30099 Classic 2017 |
| CVE-2018-12849US | high7.5 | 33.6% (98th) | — | ✗no fix | 2018-09-25 | ≤ 2017.011.30099 Classic 2017 |
| CVE-2018-5065US | high8.8 | 31.2% (98th) | — | ✗no fix | 2018-07-20 | ≤ 2017.011.30080 Classic 2017 |
| CVE-2018-5063US | medium6.5 | 30.7% (98th) | — | ✗no fix | 2018-07-20 | ≤ 2017.011.30080 Classic 2017 |
| CVE-2018-12764US | medium6.5 | 30.7% (98th) | — | ✗no fix | 2018-07-20 | ≤ 2017.011.30080 Classic 2017 |
| CVE-2021-44709US | high7.8 | 29.0% (98th) | — | ✗no fix | 2022-01-14 | ≤ 17.011.30207 Classic 2017 |
| CVE-2018-12840US | high7.5 | 28.8% (98th) | — | ✗no fix | 2018-09-25 | ≤ 2017.011.30099 Classic 2017 |
| CVE-2018-15937US | high7.8 | 28.0% (98th) | — | ✗no fix | 2018-10-12 | ≤ 2017.011.30102 Classic 2017 |
| CVE-2018-15931US | high7.8 | 27.8% (98th) | — | ✗no fix | 2018-10-12 | ≤ 2017.011.30102 Classic 2017 |
| CVE-2018-15930US | high7.8 | 27.8% (98th) | — | ✗no fix | 2018-10-12 | ≤ 2017.011.30102 Classic 2017 |
| CVE-2018-5068US | high7.5 | 27.4% (98th) | — | ✗no fix | 2018-07-20 | ≤ 2017.011.30080 Classic 2017 |
| CVE-2018-12768US | high7.5 | 27.4% (98th) | — | ✗no fix | 2018-07-20 | ≤ 2017.011.30080 Classic 2017 |
| CVE-2018-12767US | high7.5 | 27.4% (98th) | — | ✗no fix | 2018-07-20 | ≤ 2017.011.30080 Classic 2017 |
| CVE-2018-12766US | high7.5 | 27.4% (98th) | — | ✗no fix | 2018-07-20 | ≤ 2017.011.30080 Classic 2017 |
| CVE-2018-12765US | high7.5 | 27.4% (98th) | — | ✗no fix | 2018-07-20 | ≤ 2017.011.30080 Classic 2017 |
| CVE-2018-5070US | critical9.8 | 25.1% (98th) | — | ✗no fix | 2018-07-20 | ≤ 2017.011.30080 Classic 2017 |