| CVE-2026-31431US | —OT critical | 98.1% (100th) | KEV | ✗no fix | 2026-04-22 | ≤ vers:unknown/* |
| CVE-2023-0266US | high7.0OT critical | 3.67% (90th) | KEV | ✓56b88b50565cd8b946a2d00b0c83927b7ebb055e | 2023-01-30 | 4.14 → 56b88b50565cd8b946a2d00b0c83927b7ebb055e |
| CVE-2019-11477US | high7.5 | 98.7% (100th) | Exploit | ✓5.1.11 | 2019-06-19 | 5 versions |
| CVE-2021-3490US | high7.8 | 27.4% (98th) | Exploit | ✓v5.12.4 | 2021-06-04 | 5 versions |
| CVE-2023-2163US | high8.8 | 3.64% (89th) | Exploit | ✓71b547f561247897a0a14f3082730156c0533fed | 2023-09-20 | 0 → 71b547f561247897a0a14f3082730156c0533fed |
| CVE-2022-42896US | high8.8 | 2.45% (84th) | Exploit | ✗no fix | 2022-11-23 | ≤ 3.0.0 ≤711f8c3fb3db61897080468586b970c87c61d9e4 |
| CVE-2023-0045US | high7.5 | 2.40% (84th) | Exploit | ✓a664ec9158eeddd75121d39c9a0758016097fa96 | 2023-04-25 | 9137bb27e60e → a664ec9158eeddd75121d39c9a0758016097fa96 |
| CVE-2023-35001US | high7.8 | 1.54% (75th) | Exploit | ✗no fix | 2023-07-05 | ≤ v3.13-rc1 |
| CVE-2023-1998US | medium5.6 | 1.38% (72nd) | Exploit | ✓6.3 | 2023-04-21 | 0 → 6.3 |
| CVE-2023-1829US | high7.8 | 1.06% (64th) | Exploit | ✓6.1.18 | 2023-04-12 | 7 versions |
| CVE-2022-3910US | high7.8 | 1.05% (64th) | Exploit | ✗no fix | 2022-11-22 | ≤ 5.18.0 ≤5.19.10 |
| CVE-2023-3390US | high7.8 | 0.91% (60th) | Exploit | ✓5.10.188 | 2023-06-28 | 7 versions |
| CVE-2023-6931US | high7.0 | 0.71% (54th) | Exploit | ✓5.4.264 | 2023-12-19 | 6 versions |
| CVE-2023-0461US | high7.8 | 0.65% (51st) | Exploit | ✓2c02d41d71f90a5168391b6a5f2954112ba2307c | 2023-02-28 | 0 → 2c02d41d71f90a5168391b6a5f2954112ba2307c |
| CVE-2023-1281US | high7.8 | 0.30% (23rd) | Exploit | ✓5.10.169 | 2023-03-22 | 3 versions |
| CVE-2019-11478US | high7.5 | 94.7% (100th) | — | ✓4.9.182 | 2019-06-19 | 5 versions |
| CVE-2019-11479US | high7.5 | 91.7% (100th) | — | ✓4.19.52 | 2019-06-19 | 5 versions |
| CVE-2018-5390US | high7.5 | 71.8% (99th) | — | ✓4.9* | 2018-08-06 | 4.9 → 4.9* |
| CVE-2023-31248US | high7.8 | 1.89% (79th) | — | ✗no fix | 2023-07-05 | ≤ v5.9-rc1 |
| CVE-2024-24860US | medium5.3 | 0.80% (57th) | — | ✓v6.8-rc1 | 2024-02-05 | 2 versions |
| CVE-2023-0458US | medium4.7 | 0.73% (54th) | — | ✗no fix | 2023-04-26 | ≤ 0 ≤6.1.8 |
| CVE-2024-24859US | medium4.8 | 0.71% (53rd) | — | ✓v6.8-rc2 | 2024-02-05 | v4.0-rc1 → v6.8-rc2 |
| CVE-2021-3491US | high8.8 | 0.64% (51st) | — | ✓v5.12.4 | 2021-06-04 | 5 versions |
| CVE-2023-0459US | medium5.5 | 0.64% (50th) | — | ✗no fix | 2023-05-25 | ≤ 4b842e4e25b12951fa10dedb4bc16bc47e3b850c ≤74e19ef0ff8061ef55957c3abd71614ef0f42f47 |
| CVE-2024-22099US | medium5.5 | 0.61% (49th) | — | ✓v6.8-rc1 | 2024-01-25 | v2.6.12-rc2 → v6.8-rc1 |
| CVE-2024-23307US | high7.8 | 0.58% (48th) | — | ✓v6.8-rc1 | 2024-01-25 | v4.1-rc1 → v6.8-rc1 |
| CVE-2021-3489US | high7.8 | 0.55% (46th) | — | ✓v5.12.4 | 2021-06-04 | 5 versions |
| CVE-2024-21803US | high7.8 | 0.50% (42nd) | — | ✓v6.8-rc1 | 2024-01-30 | 2 versions |
| CVE-2022-42895US | medium6.5 | 0.47% (41st) | — | ✗no fix | 2022-11-23 | ≤ 3.0.0 ≤b1a2cd50c0357f243b7435a732b4e62ba3157a2e |
| CVE-2022-4696US | high7.8 | 0.44% (38th) | — | ✗no fix | 2023-01-11 | ≤ 5.7-rc1 ≤5.10.159 |
| CVE-2023-2236US | high7.8 | 0.43% (37th) | — | ✓6.1 | 2023-05-01 | 5.19 → 6.1 |
| CVE-2022-2196US | high8.8OT elevated | 0.35% (29th) | — | ✓f93a1a5bdcdd122aae0a3eab7a52c15b71fb725b | 2023-01-09 | 13 versions |
| CVE-2024-24858US | medium5.3 | 0.33% (25th) | — | ✓v6.8-rc2 | 2024-02-05 | v4.0-rc1 → v6.8-rc2 |
| CVE-2024-24857US | medium6.8 | 0.32% (24th) | — | ✓v6.8-rc2 | 2024-02-05 | v4.0-rc1 → v6.8-rc2 |
| CVE-2023-1872US | high7.0 | 0.31% (23rd) | — | ✗no fix | 2023-04-12 | ≤ 5.7 ≤5.17 |
| CVE-2023-0240US | high7.8 | 0.27% (19th) | — | ✗no fix | 2023-01-30 | ≤ 5.10 ≤5.10.161 |
| CVE-2023-23586US | medium5.5 | 0.27% (19th) | — | ✗no fix | 2023-02-17 | ≤ 5.6 ≤5.10.161 |
| CVE-2023-2235US | high7.8 | 0.25% (16th) | — | ✓6.3 | 2023-05-01 | 5.13 → 6.3 |
| CVE-2023-1295US | high7.0 | 0.22% (12th) | — | ✗no fix | 2023-06-28 | ≤ 5.6 ≤5.11 |
| CVE-2024-24861US | medium6.3 | 0.21% (10th) | — | ✓v6.8-rc1 | 2024-02-05 | 2 versions |
| CVE-2024-24855US | medium4.7 | 0.18% (8th) | — | ✓v6.5-rc2 | 2024-02-05 | v2.6.34-rc2 → v6.5-rc2 |
| CVE-2024-24864US | medium4.7 | 0.18% (8th) | — | ✓v6.8-rc2 | 2024-02-05 | 2 versions |
| CVE-2024-23196US | medium4.7 | 0.17% (6th) | — | ✓v6.5-rc1 | 2024-02-05 | 2 versions |
| CVE-2024-22386US | medium4.7 | 0.16% (5th) | — | ✓v6.6-rc1 | 2024-02-05 | 2 versions |
| CVE-2024-24863US | — | — | — | ✗no fix | 2024-04-14 | — |
| CVE-2024-24862US | — | — | — | ✗no fix | 2024-04-14 | — |