| CVE-2026-33032US | —OT elevated | 35.3% (98th) | Exploit | ✗no fix | 2026-03-30 | 2 versions |
| CVE-2026-27944US | —OT elevated | 22.9% (98th) | Exploit | ✓2.3.3 | 2026-03-05 | 2 versions |
| CVE-2024-22198US | high8.8 | 4.06% (91st) | Exploit | ✓1.9.10-0.20231219184941-827e76c46e63 | 2024-01-11 | < 1.9.10-0.20231219184941-827e76c46e63 |
| CVE-2026-42221US | critical9.8OT high | 1.34% (71st) | Exploit | ✓2.3.8 | 2026-05-04 | 2 versions |
| CVE-2026-107806US | high7.2 | 0.57% (47th) | Exploit | ✓1.9.10-0.20260728074146-a467ed652591 | 2026-10-09 | 1.9.10-0.20260421071512-7864e378f5cf → 1.9.10-0.20260728074146-a467ed652591 |
| CVE-2024-22197US | high8.8 | 1.54% (75th) | — | ✓1.9.10-0.20231219184941-827e76c46e63 | 2024-01-11 | < 1.9.10-0.20231219184941-827e76c46e63 |
| CVE-2024-23828US | high8.8 | 1.05% (64th) | — | ✓1.9.10-0.20240126104956-d70e37c8575e | 2024-01-29 | 2 versions |
| CVE-2026-33029US | medium6.5 | 0.98% (62nd) | — | ✗no fix | 2026-03-30 | 2 versions |
| CVE-2026-84318US | — | 0.82% (57th) | — | ✓1.9.10-0.20260703131214-23d1934099b0 | 2026-10-12 | 1.9.10-0.20250506154222-1330888280a2 → 1.9.10-0.20260703131214-23d1934099b0 |
| CVE-2024-23827US | critical9.8 | 0.70% (53rd) | — | ✓1.9.10-0.20240128060047-8581bdd3c6f4 | 2024-01-29 | 2 versions |
| CVE-2024-22196US | medium6.5 | 0.58% (48th) | — | ✓1.9.10-0.20231219195202-ec93ab05a3ec | 2024-01-11 | < 1.9.10-0.20231219195202-ec93ab05a3ec |
| CVE-2026-33028US | high7.5 | 0.55% (46th) | — | ✗no fix | 2026-03-30 | 2 versions |
| CVE-2026-84313US | —OT elevated | 0.54% (45th) | — | ✗no fix | 2026-10-12 | — |
| CVE-2026-84316US | — | 0.51% (43rd) | — | ✓1.9.10-0.20260703131214-23d1934099b0 | 2026-10-12 | < 1.9.10-0.20260703131214-23d1934099b0 |
| CVE-2026-84317US | — | 0.48% (41st) | — | ✓1.9.10-0.20260703131214-23d1934099b0 | 2026-10-12 | < 1.9.10-0.20260703131214-23d1934099b0 |
| CVE-2026-107805US | — | 0.47% (40th) | — | ✓1.9.10-0.20260901043436-8c9b9a1aff21 | 2026-10-09 | 1.9.10-0.20260729084040-acb59fdd81db → 1.9.10-0.20260901043436-8c9b9a1aff21 |
| CVE-2026-107810US | — | 0.45% (38th) | — | ✓1.9.10-0.20260728074146-a467ed652591 | 2026-10-09 | 1.9.10-0.20250517140552-daee3ac7ade1 → 1.9.10-0.20260728074146-a467ed652591 |
| CVE-2026-107811US | —OT elevated | 0.43% (38th) | — | ✓1.9.10-0.20260728091109-0ecbd106c37b | 2026-10-09 | 1.9.10-0.20250517140552-daee3ac7ade1 → 1.9.10-0.20260728091109-0ecbd106c37b |
| CVE-2026-84360US | —OT elevated | 0.42% (36th) | — | ✓1.9.10-0.20260703131214-23d1934099b0 | 2026-10-12 | < 1.9.10-0.20260703131214-23d1934099b0 |
| CVE-2026-84314US | —OT elevated | 0.42% (36th) | — | ✓1.9.10-0.20260703131214-23d1934099b0 | 2026-10-12 | < 1.9.10-0.20260703131214-23d1934099b0 |
| CVE-2026-33027US | medium6.5 | 0.41% (35th) | — | ✗no fix | 2026-03-30 | 2 versions |
| CVE-2026-107808US | — | 0.41% (35th) | — | ✓1.9.10-0.20260728074558-95cd21b70814 | 2026-10-09 | 1.9.10-0.20250517140552-daee3ac7ade1 → 1.9.10-0.20260728074558-95cd21b70814 |
| CVE-2026-84315US | —OT elevated | 0.34% (27th) | — | ✓1.9.10-0.20260703131214-23d1934099b0 | 2026-10-12 | < 1.9.10-0.20260703131214-23d1934099b0 |
| CVE-2026-33026US | critical9.1OT elevated | 0.33% (27th) | — | ✓1.9.10-0.20260315015203-f61bcec547c0 | 2026-03-30 | 2 versions |
| CVE-2026-44015US | critical9.9 | 0.32% (25th) | — | ✗no fix | 2026-05-12 | 2 versions |
| CVE-2026-107813US | —OT elevated | 0.30% (23rd) | — | ✓1.9.10-0.20260728074433-a3999bd78a3b | 2026-10-09 | 1.9.10-0.20250517140552-daee3ac7ade1 → 1.9.10-0.20260728074433-a3999bd78a3b |
| CVE-2026-42220US | —OT elevated | 0.30% (22nd) | — | ✗no fix | 2026-05-04 | 2 versions |
| CVE-2026-107807US | —OT elevated | 0.30% (22nd) | — | ✓1.9.10-0.20260728074433-a3999bd78a3b | 2026-10-09 | 1.9.10-0.20250517140552-daee3ac7ade1 → 1.9.10-0.20260728074433-a3999bd78a3b |
| CVE-2026-84319US | — | 0.28% (20th) | — | ✓1.9.10-0.20260703131214-23d1934099b0 | 2026-10-12 | < 1.9.10-0.20260703131214-23d1934099b0 |
| CVE-2026-33031US | high8.1OT elevated | 0.27% (20th) | — | ✓1.9.10-0.20260314152518-7b66578adb47 | 2026-04-20 | < 1.9.10-0.20260314152518-7b66578adb47 |
| CVE-2026-107809US | — | 0.23% (13th) | — | ✓1.9.10-0.20260728074433-a3999bd78a3b | 2026-10-09 | 1.9.10-0.20250517140552-daee3ac7ade1 → 1.9.10-0.20260728074433-a3999bd78a3b |
| CVE-2026-107804US | — | 0.22% (12th) | — | ✓1.9.10-0.20260904075558-e30e331303fc | 2026-10-09 | 2 versions |
| CVE-2026-84321US | — | 0.21% (11th) | — | ✓1.9.10-0.20260703131214-23d1934099b0 | 2026-10-12 | < 1.9.10-0.20260703131214-23d1934099b0 |
| CVE-2026-34403US | high8.1 | 0.18% (7th) | — | ✓1.9.10-0.20260316053337-1a9cd29a3082 | 2026-04-20 | < 1.9.10-0.20260316053337-1a9cd29a3082 |
| CVE-2026-107812US | —OT elevated | 0.18% (7th) | — | ✓1.9.10-0.20260728114330-580585516dd8 | 2026-10-09 | 1.9.10-0.20250517140552-daee3ac7ade1 → 1.9.10-0.20260728114330-580585516dd8 |
| CVE-2026-84312US | — | 0.17% (7th) | — | ✗no fix | 2026-10-12 | — |
| CVE-2026-84320US | — | 0.17% (6th) | — | ✓1.9.10-0.20260715121709-f92218e01054 | 2026-10-12 | < 1.9.10-0.20260715121709-f92218e01054 |