| CVE-2026-31431US | —OT critical | 98.1% (100th) | KEV | ✓6.1.170 | 2026-04-22 | 19 versions |
| CVE-2024-53104US | high7.8OT critical | 3.40% (89th) | KEV | ✓5.4.286 | 2024-12-02 | 20 versions |
| CVE-2025-39682US | critical9.8OT critical | 3.25% (88th) | KEV | ✓6.16.4 | 2025-09-05 | 12 versions |
| CVE-2024-36971US | high7.8OT critical | 2.70% (86th) | KEV | ✓051c0bde9f0450a2ec3d62a86d2a0d2fad117f13 | 2024-06-10 | 18 versions |
| CVE-2025-39964US | medium5.5OT critical | 1.57% (75th) | KEV | ✓1b34cbbf4f011a121ef7b2d7d6e6920a036d5285 | 2025-10-13 | 16 versions |
| CVE-2025-38352US | —OT critical | 1.36% (71st) | KEV | ✓5.4.295 | 2025-07-22 | 18 versions |
| CVE-2026-53266US | —OT critical | 0.93% (61st) | KEV | ✓b7e91939ba9be805a62a257fa4e227dffbb88fa0 | 2026-06-25 | 24 versions |
| CVE-2026-53362US | —OT critical | 0.71% (53rd) | KEV | ✓46f201f8b4c39633a1fa3dc12459f506d470993d | 2026-07-04 | 14 versions |
| CVE-2024-53197US | —OT critical | 4.12% (91st) | KEV | ✓920a369a9f014f10ec282fd298d0666129379f1b | 2024-12-27 | 20 versions |
| CVE-2024-53150US | high7.1OT critical | 1.35% (71st) | KEV | ✓45a92cbc88e4013bfed7fd2ccab3ade45f8e896b | 2024-12-24 | 22 versions |
| CVE-2024-50302US | medium5.5OT critical | 0.81% (57th) | KEV | ✓5.15.172 | 2024-11-19 | 22 versions |
| CVE-2026-43284US | — | 94.2% (100th) | Exploit | ✓6.1.172 | 2026-05-08 | 22 versions |
| CVE-2026-43500US | high7.8 | 94.1% (100th) | Exploit | ✓3711382a77342a9a1c3d2e7330dcfc7ea927f568 | 2026-05-11 | 12 versions |
| CVE-2023-52440US | high7.8 | 22.3% (98th) | Exploit | ✓ecd7e1c562cb08e41957fcd4b0e404de5ab38e20 | 2024-02-21 | 11 versions |
| CVE-2025-39946US | medium5.5 | 10.3% (96th) | Exploit | ✓6.17 | 2025-10-04 | 12 versions |
| CVE-2026-46300US | high7.8 | 10.2% (96th) | Exploit | ✓5.15.208 | 2026-05-23 | 18 versions |
| CVE-2026-46242US | — | 4.39% (91st) | Exploit | ✓7.0.10 | 2026-05-30 | 17 versions |
| CVE-2026-46333US | — | 4.30% (91st) | Exploit | ✓7.0.8 | 2026-05-15 | 26 versions |
| CVE-2024-26581US | high7.8OT elevated | 2.22% (83rd) | Exploit | ✓5.10.210 | 2024-02-20 | 23 versions |
| CVE-2025-38501US | high7.5 | 2.17% (82nd) | Exploit | ✓6.16.1 | 2025-08-16 | 14 versions |
| CVE-2026-43503US | — | 1.99% (80th) | Exploit | ✓989214c66884d70716d83dc1d0bf5e16287bf349 | 2026-05-23 | 18 versions |
| CVE-2026-74469US | — | 1.47% (74th) | Exploit | ✓6.12.103 | 2026-08-15 | 12 versions |
| CVE-2026-64564US | — | 1.43% (73rd) | Exploit | ✓7.2 | 2026-08-04 | 12 versions |
| CVE-2026-53359US | — | 1.37% (72nd) | Exploit | ✓5e470998a23e4c3d89ed24e8172cb22747e61efa | 2026-07-04 | 14 versions |
| CVE-2024-36886US | high7.8 | 1.31% (70th) | Exploit | ✓6.8.10 | 2024-05-30 | 18 versions |
| CVE-2026-31402US | — | 1.20% (68th) | Exploit | ✓6.1.167 | 2026-04-03 | 18 versions |
| CVE-2026-23231US | high7.8 | 1.03% (63rd) | Exploit | ✓6.18.14 | 2026-03-04 | 14 versions |
| CVE-2026-31635US | — | 1.02% (63rd) | Exploit | ✓beee051f259acd286fed64c32c2b31e6f5097eb5 | 2026-04-24 | 8 versions |
| CVE-2023-52654US | medium4.7OT elevated | 0.89% (59th) | Exploit | ✓5.15.143 | 2024-05-14 | 21 versions |
| CVE-2026-43499US | — | 0.89% (59th) | Exploit | ✓5.10.261 | 2026-05-21 | 18 versions |
| CVE-2025-21756US | — | 0.89% (59th) | Exploit | ✓3f43540166128951cc1be7ab1ce6b7f05c670d8b | 2025-02-27 | 16 versions |
| CVE-2024-44947US | medium5.5 | 0.89% (59th) | Exploit | ✓18a067240817bee8a9360539af5d79a4bf5398a5 | 2024-09-02 | 18 versions |
| CVE-2025-37899US | high7.8 | 0.88% (59th) | Exploit | ✓02d16046cd11a5c037b28c12ffb818c56dd3ef43 | 2025-05-20 | 12 versions |
| CVE-2024-44946US | medium5.5 | 0.86% (58th) | Exploit | ✓807067bf014d4a3ae2cc55bd3de16f22a01eb580 | 2024-08-31 | 18 versions |
| CVE-2024-27398US | high7.8 | 0.83% (57th) | Exploit | ✓6.8.10 | 2024-05-14 | 27 versions |
| CVE-2024-26817US | medium5.5 | 0.76% (55th) | Exploit | ✓6.8.6 | 2024-04-13 | 18 versions |
| CVE-2025-37928US | high7.8 | 0.74% (54th) | Exploit | ✓6.6.90 | 2025-05-20 | 12 versions |
| CVE-2026-43501US | — | 0.73% (54th) | Exploit | ✓7.0.4 | 2026-05-21 | 18 versions |
| CVE-2026-52924US | — | 0.66% (51st) | Exploit | ✓1d4652f677906a64487c13f9ace54b0eb263b5d0 | 2026-06-24 | 18 versions |
| CVE-2025-37947US | high7.8 | 0.66% (51st) | Exploit | ✓0ca6df4f40cf4c32487944aaf48319cb6c25accc | 2025-05-20 | 12 versions |
| CVE-2026-46331US | — | 0.64% (50th) | Exploit | ✓d5d01d35a5a7d36f7cb679b67d9cbdd5205672dc | 2026-06-16 | 26 versions |
| CVE-2025-21692US | high7.8 | 0.62% (49th) | Exploit | ✓1332c6ed446be787f901ed1064ec6a3c694f028a | 2025-02-10 | 16 versions |
| CVE-2026-68376US | — | 0.60% (49th) | Exploit | ✓a8d20ba0ab518c9ccbcde258f25fc1ee6e51d5db | 2026-08-10 | 12 versions |
| CVE-2026-23003US | medium5.5 | 0.55% (46th) | Exploit | ✓6.12.67 | 2026-01-25 | 22 versions |
| CVE-2025-38089US | medium5.5 | 0.55% (46th) | Exploit | ✓c90459cd58bb421d275337093d8e901e0ba748dd | 2025-06-30 | 12 versions |
| CVE-2026-68136US | — | 0.54% (45th) | Exploit | ✓6.18.42 | 2026-08-10 | 10 versions |
| CVE-2024-50251US | medium6.2 | 0.53% (45th) | Exploit | ✓0ab3be58b45b996764aba0187b46de19b3e58a72 | 2024-11-09 | 18 versions |
| CVE-2026-23111US | high7.8 | 0.52% (44th) | Exploit | ✓6.12.70 | 2026-02-13 | 24 versions |
| CVE-2025-38001US | medium5.5 | 0.52% (44th) | Exploit | ✓4e38eaaabfb7fffbb371a51150203e19eee5d70e | 2025-06-06 | 20 versions |
| CVE-2026-64560US | — | 0.50% (43rd) | Exploit | ✓5.15.213 | 2026-07-29 | 18 versions |