| CVE-2021-21017US | medium6.8OT critical | 86.3% (100th) | KEV | ✗no fix | 2021-02-11 | ≤ 2021.001.20135 Continuous |
| CVE-2020-9715US | high7.8OT critical | 33.5% (98th) | KEV | ✗no fix | 2020-08-19 | ≤ 2020.012.20041 Continuous |
| CVE-2026-34621US | —OT critical | 7.23% (94th) | KEV | ✗no fix | 2026-04-11 | ≤ 26.001.21411 |
| CVE-2021-28550US | high8.8OT critical | 51.9% (99th) | KEV | ✗no fix | 2021-09-02 | ≤ 2021.001.20155 Continuous |
| CVE-2018-4990US | high8.8OT critical | 35.9% (98th) | KEV | ✗no fix | 2018-07-09 | 2 versions |
| CVE-2023-26369US | —OT critical | 6.75% (94th) | KEV | ✗no fix | 2023-09-13 | ≤ 23.003.20284 Continuous |
| CVE-2019-8050US | critical9.8 | 40.6% (99th) | Exploit | ✗no fix | 2019-08-20 | 3 versions |
| CVE-2019-16451US | critical9.8 | 34.7% (98th) | Exploit | ✗no fix | 2019-12-19 | ≤ 2019.021.20058 Continuous |
| CVE-2019-8048US | critical9.8 | 34.6% (98th) | Exploit | ✗no fix | 2019-08-20 | 3 versions |
| CVE-2019-8196US | critical9.8 | 22.9% (98th) | Exploit | ✗no fix | 2019-10-17 | ≤ 2019.021.20047 Continuous |
| CVE-2019-8195US | critical9.8 | 22.9% (98th) | Exploit | ✗no fix | 2019-10-17 | ≤ 2019.012.20040 Continuous |
| CVE-2019-8016US | critical9.8 | 22.0% (98th) | Exploit | ✗no fix | 2019-08-20 | 3 versions |
| CVE-2019-8049US | critical9.8 | 19.7% (97th) | Exploit | ✗no fix | 2019-08-20 | 3 versions |
| CVE-2019-8197US | critical9.8 | 16.8% (97th) | Exploit | ✗no fix | 2019-10-17 | ≤ 2019.012.20040 Continuous |
| CVE-2019-8045US | critical9.8 | 16.0% (97th) | Exploit | ✗no fix | 2019-08-20 | 2 versions |
| CVE-2021-21042US | medium6.5 | 14.7% (97th) | Exploit | ✗no fix | 2021-02-11 | ≤ 2021.001.20135 Continuous |
| CVE-2019-8044US | critical9.8 | 14.5% (97th) | Exploit | ✗no fix | 2019-08-20 | 2 versions |
| CVE-2019-8043US | high7.5 | 13.4% (96th) | Exploit | ✗no fix | 2019-08-20 | ≤ 2019.012.20036 Continuous |
| CVE-2021-39863US | medium6.8 | 13.2% (96th) | Exploit | ✗no fix | 2021-09-29 | 2 versions |
| CVE-2019-8014US | high8.8 | 8.75% (95th) | Exploit | ✗no fix | 2019-08-20 | 3 versions |
| CVE-2021-21086US | high7.8 | 4.71% (92nd) | Exploit | ✗no fix | 2021-09-02 | ≤ 2021.001.20155 Continuous |
| CVE-2019-7069US | high8.8 | 4.51% (91st) | Exploit | ✗no fix | 2019-05-24 | ≤ 2019.010.20091 Continuous |
| CVE-2021-45067US | medium5.5 | 3.56% (89th) | Exploit | ✗no fix | 2022-01-14 | ≤ 21.011.20039 Continuous |
| CVE-2021-39843US | medium6.8 | 76.7% (100th) | — | ✗no fix | 2021-09-29 | ≤ 2021.007.20091Continuous |
| CVE-2021-39836US | high7.8 | 69.5% (99th) | — | ✗no fix | 2021-09-29 | ≤ 2021.007.20091Continuous |
| CVE-2021-28560US | medium6.8 | 66.9% (99th) | — | ✗no fix | 2021-09-02 | ≤ 2021.001.20155 Continuous |
| CVE-2021-28639US | high9.3 | 66.1% (99th) | — | ✗no fix | 2021-08-20 | ≤ 2021.005.20058 Continuous |
| CVE-2021-39839US | medium6.8 | 65.2% (99th) | — | ✗no fix | 2021-09-29 | ≤ 2021.007.20091Continuous |
| CVE-2021-39838US | medium6.8 | 65.2% (99th) | — | ✗no fix | 2021-09-29 | ≤ 2021.007.20091Continuous |
| CVE-2021-39837US | medium6.8 | 65.2% (99th) | — | ✗no fix | 2021-09-29 | ≤ 2021.007.20091Continuous |
| CVE-2021-39840US | medium6.8 | 60.8% (99th) | — | ✗no fix | 2021-09-29 | ≤ 2021.007.20091Continuous |
| CVE-2021-44703US | high7.8 | 57.3% (99th) | — | ✗no fix | 2022-01-14 | ≤ 21.011.20039 Continuous |
| CVE-2019-7111US | high8.8 | 55.7% (99th) | — | ✗no fix | 2019-05-23 | 2 versions |
| CVE-2021-40728US | medium6.8 | 54.6% (99th) | — | ✗no fix | 2021-10-15 | ≤ 21.007.20099 Continuous |
| CVE-2021-28640US | medium6.0 | 53.4% (99th) | — | ✗no fix | 2021-08-20 | ≤ 2021.005.20058 Continuous |
| CVE-2020-24435US | high7.8 | 52.7% (99th) | — | ✗no fix | 2020-11-05 | ≤ 2020.013.20064 Continuous |
| CVE-2021-28635US | high9.3 | 51.2% (99th) | — | ✗no fix | 2021-08-20 | ≤ 2021.005.20058 Continuous |
| CVE-2020-24437US | high7.8 | 46.5% (99th) | — | ✗no fix | 2020-11-05 | ≤ 2020.013.20064 Continuous |
| CVE-2021-28554US | high7.8 | 46.0% (99th) | — | ✗no fix | 2021-08-24 | 2 versions |
| CVE-2021-44708US | high7.8 | 38.2% (99th) | — | ✗no fix | 2022-01-14 | ≤ 21.011.20039 Continuous |
| CVE-2018-4985US | high7.5 | 36.4% (98th) | — | ✗no fix | 2018-07-09 | 2 versions |
| CVE-2018-12848US | critical9.8 | 34.7% (98th) | — | ✗no fix | 2018-09-25 | 2 versions |
| CVE-2018-12850US | high7.5 | 33.6% (98th) | — | ✗no fix | 2018-09-25 | 2 versions |
| CVE-2018-12849US | high7.5 | 33.6% (98th) | — | ✗no fix | 2018-09-25 | 2 versions |
| CVE-2018-5065US | high8.8 | 31.2% (98th) | — | ✗no fix | 2018-07-20 | 2 versions |
| CVE-2018-5063US | medium6.5 | 30.7% (98th) | — | ✗no fix | 2018-07-20 | 2 versions |
| CVE-2018-12764US | medium6.5 | 30.7% (98th) | — | ✗no fix | 2018-07-20 | 2 versions |
| CVE-2021-44709US | high7.8 | 29.0% (98th) | — | ✗no fix | 2022-01-14 | ≤ 21.011.20039 Continuous |
| CVE-2018-12840US | high7.5 | 28.8% (98th) | — | ✗no fix | 2018-09-25 | 2 versions |
| CVE-2018-15937US | high7.8 | 28.0% (98th) | — | ✗no fix | 2018-10-12 | 2 versions |