| CVE-2025-59287US | —OT critical | 100.0% (100th) | KEV | ✓10.0.26100.6905 | 2025-10-14 | 4 versions |
| CVE-2025-33053US | —OT critical | 87.0% (100th) | KEV | ✓10.0.26100.4349 | 2025-06-10 | 3 versions |
| CVE-2024-43451US | —OT critical | 84.3% (100th) | KEV | ✓10.0.26100.2314 | 2024-11-12 | 10.0.26100.0 → 10.0.26100.2314 |
| CVE-2025-33073US | —OT critical | 82.7% (100th) | KEV | ✓10.0.26100.4349 | 2025-06-10 | 3 versions |
| CVE-2026-33824US | —OT critical | 77.1% (100th) | KEV | ✓10.0.26100.32690 | 2026-04-14 | 4 versions |
| CVE-2026-32202US | —OT critical | 70.9% (99th) | KEV | ✓10.0.26100.33158 | 2026-04-14 | 4 versions |
| CVE-2025-24054US | medium5.4OT critical | 62.3% (99th) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 4 versions |
| CVE-2026-21510US | —OT critical | 61.2% (99th) | KEV | ✓10.0.26100.32370 | 2026-02-10 | 2 versions |
| CVE-2013-3900US | high7.6OT critical | 44.6% (99th) | KEV | ✗no fix | 2013-12-11 | ≤ N/A |
| CVE-2025-26633US | —OT critical | 30.4% (98th) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 4 versions |
| CVE-2025-30397US | —OT critical | 27.3% (98th) | KEV | ✓10.0.26100.4061 | 2025-05-13 | 2 versions |
| CVE-2024-49138US | —OT critical | 26.2% (98th) | KEV | ✓10.0.26100.2605 | 2024-12-12 | 10.0.26100.0 → 10.0.26100.2605 |
| CVE-2025-29824US | —OT critical | 19.3% (97th) | KEV | ✓10.0.26100.3775 | 2025-04-08 | 10.0.26100.0 → 10.0.26100.3775 |
| CVE-2024-49039US | —OT critical | 14.2% (97th) | KEV | ✓10.0.26100.2314 | 2024-11-12 | 10.0.26100.0 → 10.0.26100.2314 |
| CVE-2025-21333US | —OT critical | 10.1% (96th) | KEV | ✓10.0.26100.2894 | 2025-01-14 | 3 versions |
| CVE-2026-20805US | —OT critical | 7.46% (94th) | KEV | ✓10.0.26100.32230 | 2026-01-13 | 4 versions |
| CVE-2025-24990US | —OT critical | 6.37% (94th) | KEV | ✓10.0.26100.6899 | 2025-10-14 | 4 versions |
| CVE-2025-47827US | —OT critical | 4.93% (92nd) | KEV | ✗no fix | 2025-06-05 | ≤ vers:unknown/* |
| CVE-2025-60710US | —OT critical | 4.61% (92nd) | KEV | ✓10.0.26100.7462 | 2025-11-11 | 2 versions |
| CVE-2025-62215US | —OT critical | 4.46% (91st) | KEV | ✓10.0.26100.7171 | 2025-11-11 | 2 versions |
| CVE-2026-21533US | —OT critical | 4.18% (91st) | KEV | ✓10.0.26100.32370 | 2026-02-10 | 2 versions |
| CVE-2025-24985US | —OT critical | 3.89% (90th) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 4 versions |
| CVE-2025-62221US | —OT critical | 2.50% (85th) | KEV | ✓10.0.26100.7462 | 2025-12-09 | 2 versions |
| CVE-2025-30400US | —OT critical | 1.92% (80th) | KEV | ✓10.0.26100.4061 | 2025-05-13 | 2 versions |
| CVE-2025-32709US | —OT critical | 1.82% (79th) | KEV | ✓10.0.26100.4061 | 2025-05-13 | 2 versions |
| CVE-2026-81963US | high7.8OT critical | 0.39% (33rd) | KEV | ✓10.0.26100.33438 | 2026-09-08 | 2 versions |
| CVE-2026-68820US | —OT critical | 0.33% (26th) | KEV | ✓10.0.26100.33296 | 2026-08-11 | 4 versions |
| CVE-2026-21513US | —OT critical | 15.9% (97th) | KEV | ✓10.0.26100.32370 | 2026-02-10 | 2 versions |
| CVE-2026-96951US | high8.8OT critical | 9.81% (96th) | KEV | ✓10.0.26100.33650 | 2026-10-13 | 2 versions |
| CVE-2026-21525US | —OT critical | 4.87% (92nd) | KEV | ✓10.0.26100.32370 | 2026-02-10 | 2 versions |
| CVE-2025-59230US | —OT critical | 2.66% (86th) | KEV | ✓10.0.26100.6899 | 2025-10-14 | 4 versions |
| CVE-2026-21519US | —OT critical | 2.48% (84th) | KEV | ✓10.0.26100.32370 | 2026-02-10 | 2 versions |
| CVE-2025-32706US | —OT critical | 2.33% (83rd) | KEV | ✓10.0.26100.4061 | 2025-05-13 | 2 versions |
| CVE-2025-21391US | —OT critical | 2.28% (83rd) | KEV | ✓10.0.26100.3194 | 2025-02-11 | 10.0.26100.0 → 10.0.26100.3194 |
| CVE-2025-24993US | —OT critical | 2.22% (83rd) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 4 versions |
| CVE-2025-21418US | —OT critical | 2.13% (82nd) | KEV | ✓10.0.26100.3194 | 2025-02-11 | 10.0.26100.0 → 10.0.26100.3194 |
| CVE-2025-24991US | —OT critical | 2.02% (81st) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 4 versions |
| CVE-2025-24984US | —OT critical | 1.99% (81st) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 4 versions |
| CVE-2025-24983US | —OT critical | 1.87% (79th) | KEV | ✗no fix | 2025-03-11 | ≤ vers:unknown/10.0.26100.0|<10.0.26100.3476 |
| CVE-2025-21334US | —OT critical | 1.57% (75th) | KEV | ✓10.0.26100.2894 | 2025-01-14 | 3 versions |
| CVE-2025-32701US | —OT critical | 1.42% (73rd) | KEV | ✓10.0.26100.4061 | 2025-05-13 | 2 versions |
| CVE-2025-21335US | —OT critical | 1.40% (72nd) | KEV | ✓10.0.26100.2894 | 2025-01-14 | 3 versions |
| CVE-2026-56155US | —OT critical | 0.35% (28th) | KEV | ✓10.0.26100.33158 | 2026-07-14 | 3 versions |
| CVE-2024-49113US | — | 83.8% (100th) | Exploit | ✓10.0.26100.2605 | 2024-12-12 | 10.0.26100.0 → 10.0.26100.2605 |
| CVE-2026-41089US | — | 79.6% (100th) | Exploit | ✓10.0.26100.32860 | 2026-05-12 | 4 versions |
| CVE-2025-21298US | — | 74.4% (99th) | Exploit | ✓10.0.26100.2894 | 2025-01-14 | 3 versions |
| CVE-2024-49112US | — | 72.2% (99th) | Exploit | ✓10.0.26100.2605 | 2024-12-12 | 10.0.26100.0 → 10.0.26100.2605 |
| CVE-2026-49160US | — | 56.6% (99th) | Exploit | ✓10.0.26100.32995 | 2026-06-09 | 4 versions |
| CVE-2025-47981US | — | 41.1% (99th) | Exploit | ✓10.0.26100.4652 | 2025-07-08 | 3 versions |
| CVE-2025-50154US | — | 29.8% (98th) | Exploit | ✓10.0.26100.4946 | 2025-08-12 | 10.0.26100.0 → 10.0.26100.4946 |