| 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.28000.1836 | 2026-04-14 | 3 versions |
| CVE-2026-32202US | —OT critical | 70.9% (99th) | KEV | ✓10.0.28000.2525 | 2026-04-14 | 3 versions |
| CVE-2026-21510US | —OT critical | 61.2% (99th) | KEV | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-21533US | —OT critical | 4.15% (91st) | KEV | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-81963US | high7.8OT critical | 0.39% (33rd) | KEV | ✓10.0.28000.2954 | 2026-09-08 | 3 versions |
| CVE-2026-68820US | —OT critical | 0.33% (26th) | KEV | ✓10.0.28000.2704 | 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.28000.3231 | 2026-10-13 | 2 versions |
| CVE-2026-21525US | —OT critical | 4.87% (92nd) | KEV | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| 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.28000.2269 | 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.28000.2269 | 2026-06-09 | 3 versions |
| CVE-2026-50507US | —OT elevated | 5.02% (92nd) | Exploit | ✓10.0.28000.2269 | 2026-06-09 | 3 versions |
| CVE-2026-24294US | — | 4.85% (92nd) | Exploit | ✓10.0.28000.1719 | 2026-03-10 | 3 versions |
| CVE-2026-40369US | — | 4.72% (92nd) | Exploit | ✓10.0.28000.2113 | 2026-05-12 | 3 versions |
| CVE-2026-33829US | — | 3.51% (89th) | Exploit | ✓10.0.28000.1836 | 2026-04-14 | 3 versions |
| CVE-2026-24291US | — | 3.30% (88th) | Exploit | ✓10.0.28000.1719 | 2026-03-10 | 3 versions |
| CVE-2026-41096US | — | 2.70% (86th) | Exploit | ✓10.0.28000.2113 | 2026-05-12 | 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.28000.1719 | 2026-03-10 | 3 versions |
| CVE-2026-21250US | — | 1.11% (66th) | Exploit | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-34348US | — | 1.00% (62nd) | Exploit | ✓10.0.28000.2113 | 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.28000.2525 | 2026-07-14 | 2 versions |
| CVE-2026-25172US | — | 0.92% (60th) | Exploit | ✓10.0.28000.1719 | 2026-03-10 | 3 versions |
| CVE-2026-49179US | — | 0.86% (58th) | Exploit | ✓10.0.28000.2704 | 2026-08-11 | 3 versions |
| CVE-2026-33827US | — | 0.84% (57th) | Exploit | ✓10.0.28000.1836 | 2026-04-14 | 3 versions |
| CVE-2026-50369US | — | 0.70% (53rd) | Exploit | ✓10.0.28000.2525 | 2026-07-14 | 2 versions |
| CVE-2026-26128US | — | 0.63% (50th) | Exploit | ✓10.0.28000.1719 | 2026-03-10 | 3 versions |
| CVE-2026-69451US | high7.1 | 0.57% (47th) | Exploit | ✓10.0.28000.2954 | 2026-09-08 | 2 versions |
| CVE-2025-10263US | — | 0.54% (45th) | Exploit | ✗no fix | 2026-06-09 | ≤ vers:unknown/* |
| CVE-2026-33826US | — | 0.53% (45th) | Exploit | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-32223US | — | 0.52% (44th) | Exploit | ✓10.0.28000.1836 | 2026-04-14 | 3 versions |
| CVE-2026-54984US | — | 0.47% (40th) | Exploit | ✓10.0.28000.2704 | 2026-08-11 | 3 versions |
| CVE-2026-50416US | low3.3 | 0.46% (39th) | Exploit | ✓10.0.28000.2525 | 2026-07-14 | 2 versions |
| CVE-2026-69328US | high7.8 | 0.46% (39th) | Exploit | ✓10.0.28000.2954 | 2026-09-08 | 2 versions |
| CVE-2026-21508US | high7.0 | 0.45% (39th) | Exploit | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-85884US | high7.8OT elevated | 0.45% (39th) | Exploit | ✓10.0.28000.3231 | 2026-10-13 | 2 versions |
| CVE-2026-26179US | — | 0.44% (38th) | Exploit | ✓10.0.28000.1836 | 2026-04-14 | 3 versions |
| CVE-2026-27912US | — | 0.41% (35th) | Exploit | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-54992US | high7.8 | 0.34% (27th) | Exploit | ✓10.0.28000.2525 | 2026-07-14 | 2 versions |
| CVE-2026-62737US | — | 0.33% (26th) | Exploit | ✓10.0.28000.2704 | 2026-08-11 | 3 versions |
| CVE-2026-62735US | — | 0.33% (26th) | Exploit | ✓10.0.28000.2704 | 2026-08-11 | 3 versions |
| CVE-2026-50402US | — | 0.33% (26th) | Exploit | ✓10.0.28000.2525 | 2026-07-14 | 2 versions |
| CVE-2026-49176US | — | 0.33% (26th) | Exploit | ✓10.0.28000.2525 | 2026-07-14 | 2 versions |
| CVE-2026-58635US | — | 0.32% (25th) | Exploit | ✓10.0.28000.2525 | 2026-07-14 | 2 versions |
showing 50 of 2,669