| CVE-2018-15961US | critical9.8OT critical | 100.0% (100th) | KEV | ✗no fix | 2018-09-25 | ≤ July 12 release (2018.0.0.310739), Update 6 and earlier, and Update 14 and earlier versions |
| CVE-2024-20767US | —OT critical | 98.5% (100th) | KEV | ✗no fix | 2024-03-18 | 3 versions |
| CVE-2023-26360US | —OT critical | 97.3% (100th) | KEV | ✗no fix | 2023-03-23 | 3 versions |
| CVE-2017-3066US | critical9.8OT critical | 90.6% (100th) | KEV | ✓11 Update 12 | 2017-04-27 | 3 versions |
| CVE-2026-48282US | —OT critical | 42.4% (99th) | KEV | ✗no fix | 2026-06-30 | 4 versions |
| CVE-2023-29300US | —OT critical | 100.0% (100th) | KEV | ✗no fix | 2023-07-12 | ≤ 0 ≤2023.0.0.330468 |
| CVE-2023-29298US | high7.5OT critical | 99.8% (100th) | KEV | ✗no fix | 2023-07-12 | ≤ 0 ≤2023.0.0.330468 |
| CVE-2023-38205US | —OT critical | 99.8% (100th) | KEV | ✗no fix | 2023-09-14 | ≤ 0 ≤cf2023U2 |
| CVE-2023-38203US | —OT critical | 97.1% (100th) | KEV | ✗no fix | 2023-07-20 | ≤ 0 ≤cf2023U1 |
| CVE-2023-26359US | —OT critical | 17.0% (97th) | KEV | ✗no fix | 2023-03-23 | 2 versions |
| CVE-2025-54988US | — | 47.9% (99th) | Exploit | ✗no fix | 2025-08-20 | 2 versions |
| CVE-2019-7839US | critical9.8 | 44.1% (99th) | Exploit | ✗no fix | 2019-06-12 | ≤ Update 3 and earlier, Update 10 and earlier, and Update 18 and earlier versions |
| CVE-2025-43564US | critical9.1OT high | 16.8% (97th) | Exploit | ✗no fix | 2025-05-13 | 4 versions |
| CVE-2023-44352US | medium6.1 | 84.8% (100th) | — | ✗no fix | 2023-11-17 | ≤ 0 ≤2021.11 |
| CVE-2022-38418US | — | 80.4% (100th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2023-44353US | — | 80.2% (100th) | — | ✗no fix | 2023-11-17 | ≤ 0 ≤2021.11 |
| CVE-2022-38421US | — | 79.6% (100th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2022-35711US | — | 73.9% (99th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2022-35690US | critical9.8 | 72.7% (99th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2019-7816US | critical9.8 | 67.8% (99th) | — | ✗no fix | 2019-05-24 | ≤ Update 2 and earlier, Update 9 and earlier, and Update 17 and earlier versions |
| CVE-2023-38204US | — | 66.9% (99th) | — | ✗no fix | 2023-09-14 | ≤ 0 ≤cf2023U2 |
| CVE-2023-44350US | — | 64.6% (99th) | — | ✗no fix | 2023-11-17 | ≤ 0 ≤2021.11 |
| CVE-2023-26361US | — | 58.7% (99th) | — | ✗no fix | 2023-03-23 | 2 versions |
| CVE-2025-43566US | — | 58.2% (99th) | — | ✗no fix | 2025-05-13 | 4 versions |
| CVE-2022-38419US | — | 53.7% (99th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2025-43562US | — | 51.0% (99th) | — | ✗no fix | 2025-05-13 | 4 versions |
| CVE-2023-44351US | — | 50.2% (99th) | — | ✗no fix | 2023-11-17 | ≤ 0 ≤2021.11 |
| CVE-2023-44355US | — | 47.2% (99th) | — | ✗no fix | 2023-11-17 | ≤ 0 ≤2021.11 |
| CVE-2022-38424US | — | 45.8% (99th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2022-38423US | — | 45.7% (99th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2022-38422US | — | 44.9% (99th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2022-28818US | medium6.1 | 44.8% (99th) | — | ✗no fix | 2022-05-12 | 3 versions |
| CVE-2022-38420US | —OT elevated | 44.7% (99th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2022-35710US | — | 43.2% (99th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2022-35712US | — | 37.4% (99th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2021-21087US | medium5.4 | 37.1% (99th) | — | ✗no fix | 2021-04-15 | 4 versions |
| CVE-2022-42341US | — | 36.1% (98th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2023-29301US | — | 34.7% (98th) | — | ✗no fix | 2023-07-12 | ≤ 0 ≤2023.0.0.330468 |
| CVE-2022-42340US | — | 34.4% (98th) | — | ✗no fix | 2022-10-14 | 3 versions |
| CVE-2025-30285US | high8.4 | 30.9% (98th) | — | ✗no fix | 2025-04-08 | ≤ 0 ≤2025.0 |
| CVE-2024-41874US | — | 30.3% (98th) | — | ✗no fix | 2024-09-13 | ≤ 0 ≤2021.15 |
| CVE-2018-15957US | critical9.8 | 28.2% (98th) | — | ✗no fix | 2018-09-25 | ≤ July 12 release (2018.0.0.310739), Update 6 and earlier, and Update 14 and earlier versions |
| CVE-2026-27305US | — | 26.3% (98th) | — | ✗no fix | 2026-04-14 | 3 versions |
| CVE-2018-15965US | critical9.8 | 25.9% (98th) | — | ✗no fix | 2018-09-25 | ≤ July 12 release (2018.0.0.310739), Update 6 and earlier, and Update 14 and earlier versions |
| CVE-2018-15959US | critical9.8 | 25.9% (98th) | — | ✗no fix | 2018-09-25 | ≤ July 12 release (2018.0.0.310739), Update 6 and earlier, and Update 14 and earlier versions |
| CVE-2018-15958US | critical9.8 | 25.9% (98th) | — | ✗no fix | 2018-09-25 | ≤ July 12 release (2018.0.0.310739), Update 6 and earlier, and Update 14 and earlier versions |
| CVE-2019-7091US | critical9.8 | 25.7% (98th) | — | ✗no fix | 2019-05-24 | ≤ Update 1 and earlier, Update 7 and earlier, and Update 15 and earlier versions |
| CVE-2025-54261US | critical10.0 | 25.3% (98th) | — | ✓2025 Update 4 | 2025-09-09 | 5 versions |
| CVE-2025-43561US | —OT elevated | 23.9% (98th) | — | ✗no fix | 2025-05-13 | 4 versions |
| CVE-2024-34112US | — | 23.7% (98th) | — | ✗no fix | 2024-06-13 | ≤ 0 ≤2021u13 |