| 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.26200.8246 | 2026-04-14 | 3 versions |
| CVE-2026-32202US | —OT critical | 70.9% (99th) | KEV | ✓10.0.26200.8875 | 2026-04-14 | 3 versions |
| CVE-2026-21510US | —OT critical | 61.2% (99th) | KEV | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-20805US | —OT critical | 7.46% (94th) | KEV | ✓10.0.26200.7623 | 2026-01-13 | 3 versions |
| CVE-2025-24990US | —OT critical | 6.37% (94th) | KEV | ✓10.0.26200.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-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.26200.9445 | 2026-09-08 | 3 versions |
| CVE-2026-68820US | —OT critical | 0.33% (26th) | KEV | ✓10.0.26200.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.26200.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.26200.6899 | 2025-10-14 | 2 versions |
| CVE-2026-21519US | —OT critical | 2.48% (84th) | KEV | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| 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-2026-49160US | — | 56.6% (99th) | Exploit | ✓10.0.26200.8655 | 2026-06-09 | 3 versions |
| CVE-2026-20841US | — | 9.01% (95th) | Exploit | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-42980US | — | 6.95% (94th) | Exploit | ✓10.0.26200.8655 | 2026-06-09 | 3 versions |
| CVE-2026-20817US | — | 5.42% (93rd) | Exploit | ✓10.0.26200.7623 | 2026-01-13 | 3 versions |
| CVE-2026-50507US | —OT elevated | 5.02% (92nd) | Exploit | ✓10.0.26200.8655 | 2026-06-09 | 3 versions |
| CVE-2026-24294US | — | 4.85% (92nd) | Exploit | ✓10.0.26200.8037 | 2026-03-10 | 3 versions |
| CVE-2026-40369US | — | 4.72% (92nd) | Exploit | ✓10.0.26200.8457 | 2026-05-12 | 3 versions |
| CVE-2026-33829US | — | 3.51% (89th) | Exploit | ✓10.0.26200.8246 | 2026-04-14 | 3 versions |
| CVE-2026-24291US | — | 3.30% (88th) | Exploit | ✓10.0.26200.8037 | 2026-03-10 | 3 versions |
| CVE-2026-20929US | — | 2.87% (87th) | Exploit | ✗no fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2026-41096US | — | 2.70% (86th) | Exploit | ✓10.0.26200.8457 | 2026-05-12 | 3 versions |
| CVE-2025-59194US | — | 2.67% (86th) | Exploit | ✓10.0.26200.6899 | 2025-10-14 | 2 versions |
| CVE-2026-20820US | — | 2.56% (85th) | Exploit | ✓10.0.26200.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.26200.8655 | 2026-05-20 | 3 versions |
| CVE-2026-21248US | — | 1.33% (71st) | Exploit | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-21244US | — | 1.33% (71st) | Exploit | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-25177US | — | 1.31% (70th) | Exploit | ✓10.0.26200.8037 | 2026-03-10 | 3 versions |
| CVE-2025-59254US | — | 1.11% (66th) | Exploit | ✓10.0.26200.6899 | 2025-10-14 | 2 versions |
| CVE-2026-21250US | — | 1.11% (66th) | Exploit | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2025-59284US | medium5.5 | 1.03% (63rd) | Exploit | ✓10.0.26200.6899 | 2025-10-14 | 2 versions |
| CVE-2025-58726US | — | 1.01% (63rd) | Exploit | ✓10.0.26200.6899 | 2025-10-14 | 2 versions |
| CVE-2026-34348US | — | 1.00% (62nd) | Exploit | ✓10.0.26200.8875 | 2026-07-14 | 2 versions |
| CVE-2026-62878US | — | 0.97% (62nd) | Exploit | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-56190US | — | 0.97% (62nd) | Exploit | ✓10.0.26200.8875 | 2026-07-14 | 2 versions |
| CVE-2026-25172US | — | 0.92% (60th) | Exploit | ✓10.0.26200.8037 | 2026-03-10 | 3 versions |
| CVE-2026-49179US | — | 0.86% (58th) | Exploit | ✓10.0.26200.9168 | 2026-08-11 | 3 versions |
| CVE-2026-33827US | — | 0.84% (57th) | Exploit | ✓10.0.26200.8246 | 2026-04-14 | 3 versions |
| CVE-2026-50369US | — | 0.70% (53rd) | Exploit | ✓10.0.26200.8875 | 2026-07-14 | 2 versions |
| CVE-2026-26128US | — | 0.63% (50th) | Exploit | ✓10.0.26200.8037 | 2026-03-10 | 3 versions |
| CVE-2026-69451US | high7.1 | 0.57% (47th) | Exploit | ✓10.0.26200.9445 | 2026-09-08 | 2 versions |
showing 50 of 2,956