| ID | severity CVSS base severity and score (0–10). | EPSS FIRST.org probability this is exploited in the next 30 days, with its percentile rank among all CVEs. | exploitable On CISA's Known Exploited Vulnerabilities list, or a public exploit is on file. | patched Whether a fixed version is on file for an affecting range. | published | affected |
|---|
| CVE-2026-33824US | —OT critical | 77.1% (100th) | KEV | ✓10.0.26100.8246 | 2026-04-14 | 3 versions |
| CVE-2026-32202US | —OT critical | 70.9% (99th) | KEV | ✓10.0.26100.8875 | 2026-04-14 | 3 versions |
| CVE-2025-24054US | medium5.4OT critical | 62.3% (99th) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 2 versions |
| CVE-2026-21510US | —OT critical | 61.2% (99th) | KEV | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2025-26633US | —OT critical | 30.4% (98th) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 2 versions |
| CVE-2025-21333US | —OT critical | 10.1% (96th) | KEV | ✓10.0.26100.2894 | 2025-01-14 | 2 versions |
| CVE-2026-20805US | —OT critical | 7.46% (94th) | KEV | ✓10.0.26100.7623 | 2026-01-13 | 3 versions |
| CVE-2025-24990US | —OT critical | 6.37% (94th) | KEV | ✓10.0.26100.6899 | 2025-10-14 | 2 versions |
| CVE-2025-60710US | —OT critical | 4.61% (92nd) | KEV | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2025-62215US | —OT critical | 4.46% (91st) | KEV | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2026-21533US | —OT critical | 4.15% (91st) | KEV | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2025-24985US | —OT critical | 3.89% (90th) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 2 versions |
| CVE-2025-62221US | —OT critical | 2.50% (85th) | KEV | ✗no fix | 2025-12-09 | ≤ vers:unknown/* |
| CVE-2026-81963US | high7.8OT critical | 0.39% (33rd) | KEV | ✓10.0.26100.9445 | 2026-09-08 | 3 versions |
| CVE-2026-68820US | —OT critical | 0.33% (26th) | KEV | ✓10.0.26100.9168 | 2026-08-11 | 3 versions |
| CVE-2026-21513US | —OT critical | 15.9% (97th) | KEV | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-96951US | high8.8OT critical | 9.81% (96th) | KEV | ✓10.0.26100.9711 | 2026-10-13 | 2 versions |
| CVE-2026-21525US | —OT critical | 4.87% (92nd) | KEV | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2025-59230US | —OT critical | 2.66% (86th) | KEV | ✓10.0.26100.6899 | 2025-10-14 | 2 versions |
| CVE-2026-21519US | —OT critical | 2.48% (84th) | KEV | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2025-24993US | —OT critical | 2.22% (83rd) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 2 versions |
| CVE-2025-24991US | —OT critical | 2.02% (81st) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 2 versions |
| CVE-2025-24984US | —OT critical | 1.99% (81st) | KEV | ✓10.0.26100.3476 | 2025-03-11 | 2 versions |
| CVE-2025-21334US | —OT critical | 1.57% (75th) | KEV | ✓10.0.26100.2894 | 2025-01-14 | 2 versions |
| CVE-2025-21335US | —OT critical | 1.40% (72nd) | KEV | ✓10.0.26100.2894 | 2025-01-14 | 2 versions |
| CVE-2026-85880US | high7.8OT critical | 0.39% (33rd) | KEV | ✗no fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2026-41089US | — | 79.6% (100th) | Exploit | ✗no fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2025-21298US | — | 74.4% (99th) | Exploit | ✓10.0.26100.2894 | 2025-01-14 | 2 versions |
| CVE-2026-49160US | — | 56.6% (99th) | Exploit | ✓10.0.26100.8655 | 2026-06-09 | 3 versions |
| CVE-2025-54918US | — | 25.3% (98th) | Exploit | ✓10.0.26100.6584 | 2025-09-09 | 2 versions |
| CVE-2025-24071US | — | 23.3% (98th) | Exploit | ✓10.0.26100.3476 | 2025-03-11 | 2 versions |
| CVE-2025-55234US | critical9.8 | 20.6% (98th) | Exploit | ✓10.0.26100.6584 | 2025-09-09 | 2 versions |
| CVE-2025-21293US | — | 15.0% (97th) | Exploit | ✓10.0.26100.6584 | 2025-01-14 | 2 versions |
| CVE-2026-20841US | — | 9.01% (95th) | Exploit | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-42980US | — | 6.95% (94th) | Exploit | ✓10.0.26100.8655 | 2026-06-09 | 3 versions |
| CVE-2026-20817US | — | 5.42% (93rd) | Exploit | ✓10.0.26100.7623 | 2026-01-13 | 3 versions |
| CVE-2026-50507US | —OT elevated | 5.02% (92nd) | Exploit | ✓10.0.26100.8655 | 2026-06-09 | 3 versions |
| CVE-2026-24294US | — | 4.85% (92nd) | Exploit | ✓10.0.26100.8037 | 2026-03-10 | 3 versions |
| CVE-2026-40369US | — | 4.72% (92nd) | Exploit | ✓10.0.26100.8457 | 2026-05-12 | 3 versions |
| CVE-2025-54110US | — | 4.72% (92nd) | Exploit | ✓10.0.26100.6584 | 2025-09-09 | 2 versions |
| CVE-2026-33829US | — | 3.51% (89th) | Exploit | ✓10.0.26100.8246 | 2026-04-14 | 3 versions |
| CVE-2026-24291US | — | 3.30% (88th) | Exploit | ✓10.0.26100.8037 | 2026-03-10 | 3 versions |
| CVE-2025-24076US | — | 3.21% (88th) | Exploit | ✓10.0.26100.3476 | 2025-03-11 | 2 versions |
| CVE-2026-20929US | — | 2.87% (87th) | Exploit | ✗no fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2026-41096US | — | 2.70% (86th) | Exploit | ✓10.0.26100.8457 | 2026-05-12 | 3 versions |
| CVE-2025-59194US | — | 2.67% (86th) | Exploit | ✓10.0.26100.6899 | 2025-10-14 | 2 versions |
| CVE-2026-20820US | — | 2.56% (85th) | Exploit | ✓10.0.26100.7623 | 2026-01-13 | 3 versions |
| CVE-2025-62454US | — | 2.29% (83rd) | Exploit | ✗no fix | 2025-12-09 | ≤ vers:unknown/* |
| CVE-2025-60719US | — | 1.93% (80th) | Exploit | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2026-45585US | — | 1.89% (79th) | Exploit | ✓10.0.26100.8655 | 2026-05-20 | 3 versions |
showing 50 of 3,168