| CVE-2023-36899US | high8.8 | 76.7% (100th) | Exploit | ✓10.0.14393.6167 | 2023-08-08 | 3.0.0.0 → 10.0.14393.6167 |
| CVE-2023-36049US | critical9.8 | 6.79% (94th) | — | ✓10.0.14393.6452 | 2023-11-14 | 3.0.0.0 → 10.0.14393.6452 |
| CVE-2022-26832US | medium5.0 | 3.61% (89th) | — | ✓10.0.14393.5066 | 2022-04-15 | 3.0.0.0 → 10.0.14393.5066 |
| CVE-2020-16937US | medium4.3 | 3.29% (88th) | — | ✓publication | 2020-10-16 | 3.0.0.0 → publication |
| CVE-2022-21911US | medium5.0 | 3.05% (88th) | — | ✓10.0.14393.4886 | 2022-01-11 | 3.0.0.0 → 10.0.14393.4886 |
| CVE-2023-36560US | high8.8 | 2.91% (87th) | — | ✓10.0.14393.6452 | 2023-11-14 | 3.0.0.0 → 10.0.14393.6452 |
| CVE-2023-29331US | — | 2.63% (85th) | — | ✓10.0.14393.5989 | 2023-06-14 | 3.0.0.0 → 10.0.14393.5989 |
| CVE-2025-21176US | — | 2.38% (84th) | — | ✓10.0.14393.7699 | 2025-01-14 | 3 versions |
| CVE-2023-32030US | — | 2.22% (83rd) | — | ✓10.0.14393.5989 | 2023-06-14 | 3.0.0.0 → 10.0.14393.5989 |
| CVE-2023-24936US | — | 1.56% (75th) | — | ✓10.0.14393.5989 | 2023-06-14 | 3.0.0.0 → 10.0.14393.5989 |
| CVE-2023-36873US | medium5.9 | 1.50% (74th) | — | ✓10.0.14393.6167 | 2023-08-08 | 3.0.0.0 → 10.0.14393.6167 |
| CVE-2026-83520US | high8.8 | 1.44% (73rd) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-70035US | high8.8 | 1.44% (73rd) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-69651US | high7.5 | 1.25% (69th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-58280US | high7.5 | 1.25% (69th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2023-36796US | —OT elevated | 1.23% (69th) | — | ✓10.0.14393.6252 | 2023-09-12 | 3.0.0.0 → 10.0.14393.6252 |
| CVE-2023-36794US | —OT elevated | 1.23% (69th) | — | ✓10.0.14393.6252 | 2023-09-12 | 3.0.0.0 → 10.0.14393.6252 |
| CVE-2023-36793US | —OT elevated | 1.23% (69th) | — | ✓10.0.14393.6252 | 2023-09-12 | 3.0.0.0 → 10.0.14393.6252 |
| CVE-2023-36792US | —OT elevated | 1.23% (69th) | — | ✓10.0.14393.6252 | 2023-09-12 | 3.0.0.0 → 10.0.14393.6252 |
| CVE-2026-96960US | high7.5 | 1.20% (68th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-96958US | high7.5 | 1.20% (68th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2023-24897US | — | 1.18% (68th) | — | ✓10.0.14393.5989 | 2023-06-14 | 3.0.0.0 → 10.0.14393.5989 |
| CVE-2020-1476US | medium5.5 | 1.13% (66th) | — | ✓publication | 2020-08-17 | 3.0.0.0 → publication |
| CVE-2023-24895US | — | 1.06% (64th) | — | ✓10.0.14393.5989 | 2023-06-14 | 3.0.0.0 → 10.0.14393.5989 |
| CVE-2023-36788US | —OT elevated | 1.02% (63rd) | — | ✓10.0.14393.6252 | 2023-09-12 | 3.0.0.0 → 10.0.14393.6252 |
| CVE-2026-96233US | high7.5 | 0.99% (62nd) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-84008US | high7.5 | 0.99% (62nd) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-96959US | high7.5 | 0.97% (62nd) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-70174US | high8.8 | 0.91% (60th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2023-29326US | — | 0.90% (59th) | — | ✓10.0.14393.5989 | 2023-06-14 | 3.0.0.0 → 10.0.14393.5989 |
| CVE-2026-97788US | high7.5 | 0.88% (59th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-85363US | high8.8 | 0.86% (58th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2022-41064US | — | 0.84% (58th) | — | ✓10.0.14393.5501 | 2022-11-09 | 3.0.0.0 → 10.0.14393.5501 |
| CVE-2026-102869US | high8.8 | 0.84% (58th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-69522US | high8.8 | 0.84% (58th) | — | ✓2.0.50727.8984 & 3.0.30729.8980 & 4.7.4145.0 | 2026-09-08 | 2 versions |
| CVE-2026-70007US | high8.8 | 0.80% (56th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-108398US | high8.8 | 0.78% (56th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-62872US | —OT elevated | 0.78% (56th) | — | ✓2.0.50727.8984 & 3.0.30729.8980 & 4.7.4144.0 | 2026-08-11 | 3 versions |
| CVE-2026-96224US | high8.8 | 0.76% (55th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-97801US | high7.5 | 0.73% (54th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-96222US | high7.4 | 0.59% (48th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-10-13 | 2 versions |
| CVE-2026-62886US | — | 0.47% (40th) | — | ✓2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | 2026-08-11 | 2 versions |
| CVE-2026-65810US | high7.8 | 0.40% (34th) | — | ✓2.0.50727.8984 & 3.0.30729.8980 & 4.7.4144.0 | 2026-08-11 | 3 versions |
| CVE-2026-70354US | high7.8 | 0.36% (30th) | — | ✓2.0.50727.8984 & 3.0.30729.8980 & 4.7.4144.0 | 2026-08-11 | 3 versions |