| ID | Schweregrad CVSS-Basis-Schweregrad und -Wert (0–10). | EPSS FIRST.org-Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen, mit Perzentil-Rang unter allen CVEs. | ausnutzbar Auf CISAs Liste bekannter ausgenutzter Schwachstellen (KEV) oder ein öffentlicher Exploit liegt vor. | behoben Ob für einen betroffenen Bereich eine behobene Version vorliegt. | veröffentlicht | betroffen |
|---|
| CVE-2026-33824US | —OT kritisch | 77.1% (100th) | KEV | ✓10.0.26200.8246 | 2026-04-14 | < 10.0.26200.8246 |
| CVE-2026-32202US | —OT kritisch | 70.9% (99th) | KEV | ✓10.0.26200.8246 | 2026-04-14 | < 10.0.26200.8246 |
| CVE-2026-21510US | —OT kritisch | 61.2% (99th) | KEV | ✓10.0.26200.7781 | 2026-02-10 | < 10.0.26200.7781 |
| CVE-2026-20805US | —OT kritisch | 7.46% (94th) | KEV | ✓10.0.26200.7623 | 2026-01-13 | < 10.0.26200.7623 |
| CVE-2025-24990US | —OT kritisch | 6.37% (94th) | KEV | ✓10.0.26200.6899 | 2025-10-14 | < 10.0.26200.6899 |
| CVE-2025-47827US | —OT kritisch | 4.93% (92nd) | KEV | ✓10.0.26200.6899 | 2025-06-05 | < 10.0.26200.6899 |
| CVE-2025-60710US | —OT kritisch | 4.61% (92nd) | KEV | ✓10.0.26200.7392 | 2025-11-11 | < 10.0.26200.7392 |
| CVE-2025-62215US | —OT kritisch | 4.46% (91st) | KEV | ✓10.0.26200.7092 | 2025-11-11 | < 10.0.26200.7092 |
| CVE-2026-21533US | —OT kritisch | 4.18% (91st) | KEV | ✓10.0.26200.7781 | 2026-02-10 | < 10.0.26200.7781 |
| CVE-2025-62221US | —OT kritisch | 2.50% (85th) | KEV | ✓10.0.26200.7392 | 2025-12-09 | < 10.0.26200.7392 |
| CVE-2026-81963US | high7.8OT kritisch | 0.39% (33rd) | KEV | ✓10.0.26200.9445 | 2026-09-08 | < 10.0.26200.9445 |
| CVE-2026-68820US | —OT kritisch | 0.33% (26th) | KEV | ✓10.0.26200.9106 | 2026-08-11 | < 10.0.26200.9106 |
| CVE-2026-21513US | —OT kritisch | 15.9% (97th) | KEV | ✓10.0.26200.7781 | 2026-02-10 | < 10.0.26200.7781 |
| CVE-2026-96951US | high8.8OT kritisch | 9.81% (96th) | KEV | ✓10.0.26200.9711 | 2026-10-13 | < 10.0.26200.9711 |
| CVE-2026-21525US | —OT kritisch | 4.87% (92nd) | KEV | ✓10.0.26200.7781 | 2026-02-10 | < 10.0.26200.7781 |
| CVE-2025-59230US | —OT kritisch | 2.66% (86th) | KEV | ✓10.0.26200.6899 | 2025-10-14 | < 10.0.26200.6899 |
| CVE-2026-21519US | —OT kritisch | 2.48% (84th) | KEV | ✓10.0.26200.7781 | 2026-02-10 | < 10.0.26200.7781 |
| CVE-2026-49160US | — | 56.6% (99th) | Exploit | ✓10.0.26200.8655 | 2026-06-09 | < 10.0.26200.8655 |
| CVE-2026-42980US | — | 6.95% (94th) | Exploit | ✓10.0.26200.8655 | 2026-06-09 | < 10.0.26200.8655 |
| CVE-2026-20817US | — | 5.42% (93rd) | Exploit | ✓10.0.26200.7623 | 2026-01-13 | < 10.0.26200.7623 |
| CVE-2026-50507US | —OT erhöht | 5.02% (92nd) | Exploit | ✓10.0.26200.8655 | 2026-06-09 | < 10.0.26200.8655 |
| CVE-2026-24294US | — | 4.85% (92nd) | Exploit | ✓10.0.26200.7979 | 2026-03-10 | < 10.0.26200.7979 |
| CVE-2026-40369US | — | 4.72% (92nd) | Exploit | ✓10.0.26200.8390 | 2026-05-12 | < 10.0.26200.8390 |
| CVE-2026-33829US | — | 3.51% (89th) | Exploit | ✓10.0.26200.8246 | 2026-04-14 | < 10.0.26200.8246 |
| CVE-2026-24291US | — | 3.30% (88th) | Exploit | ✓10.0.26200.7979 | 2026-03-10 | < 10.0.26200.7979 |
| CVE-2026-41096US | — | 2.70% (86th) | Exploit | ✓10.0.26200.8390 | 2026-05-12 | < 10.0.26200.8390 |
| CVE-2025-59194US | — | 2.67% (86th) | Exploit | ✓10.0.26200.6899 | 2025-10-14 | < 10.0.26200.6899 |
| CVE-2026-20820US | — | 2.56% (85th) | Exploit | ✓10.0.26200.7623 | 2026-01-13 | < 10.0.26200.7623 |
| CVE-2025-62454US | — | 2.29% (83rd) | Exploit | ✓10.0.26200.7392 | 2025-12-09 | < 10.0.26200.7392 |
| CVE-2025-54100US | — | 2.23% (83rd) | Exploit | ✓10.0.26200.7456 | 2025-12-09 | < 10.0.26200.7456 |
| CVE-2025-60719US | — | 1.93% (80th) | Exploit | ✓10.0.26200.7092 | 2025-11-11 | < 10.0.26200.7092 |
| CVE-2026-45585US | — | 1.89% (79th) | Exploit | ✗kein Fix | 2026-05-20 | — |
| CVE-2026-25177US | — | 1.33% (71st) | Exploit | ✓10.0.26200.7979 | 2026-03-10 | < 10.0.26200.7979 |
| CVE-2026-21248US | — | 1.33% (71st) | Exploit | ✓10.0.26200.7781 | 2026-02-10 | < 10.0.26200.7781 |
| CVE-2026-21244US | — | 1.33% (71st) | Exploit | ✓10.0.26200.7781 | 2026-02-10 | < 10.0.26200.7781 |
| CVE-2025-59254US | — | 1.11% (66th) | Exploit | ✓10.0.26200.6899 | 2025-10-14 | < 10.0.26200.6899 |
| CVE-2026-21250US | — | 1.11% (66th) | Exploit | ✓10.0.26200.7781 | 2026-02-10 | < 10.0.26200.7781 |
| CVE-2025-59284US | medium5.5 | 1.03% (63rd) | Exploit | ✓10.0.26200.6899 | 2025-10-14 | < 10.0.26200.6899 |
| CVE-2025-58726US | — | 1.01% (63rd) | Exploit | ✓10.0.26200.6899 | 2025-10-14 | < 10.0.26200.6899 |
| CVE-2026-34348US | — | 1.00% (62nd) | Exploit | ✓10.0.26200.8875 | 2026-07-14 | < 10.0.26200.8875 |
| CVE-2026-56190US | — | 0.97% (62nd) | Exploit | ✓10.0.26200.8875 | 2026-07-14 | < 10.0.26200.8875 |
| CVE-2026-49179US | — | 0.86% (58th) | Exploit | ✓10.0.26200.9106 | 2026-08-11 | < 10.0.26200.9106 |
| CVE-2026-33827US | — | 0.84% (58th) | Exploit | ✓10.0.26200.8246 | 2026-04-14 | < 10.0.26200.8246 |
| CVE-2026-50369US | — | 0.70% (53rd) | Exploit | ✓10.0.26200.8875 | 2026-07-14 | < 10.0.26200.8875 |
| CVE-2026-26128US | — | 0.65% (51st) | Exploit | ✓10.0.26200.7979 | 2026-03-10 | < 10.0.26200.7979 |
| CVE-2026-69451US | high7.1 | 0.57% (47th) | Exploit | ✓10.0.26200.9445 | 2026-09-08 | < 10.0.26200.9445 |
| CVE-2025-60709US | — | 0.53% (45th) | Exploit | ✓10.0.26200.7092 | 2025-11-11 | < 10.0.26200.7092 |
| CVE-2026-32223US | — | 0.52% (44th) | Exploit | ✓10.0.26200.8246 | 2026-04-14 | < 10.0.26200.8246 |
| CVE-2025-62470US | — | 0.51% (43rd) | Exploit | ✓10.0.26200.7392 | 2025-12-09 | < 10.0.26200.7392 |
| CVE-2026-54984US | — | 0.47% (40th) | Exploit | ✓10.0.26200.9106 | 2026-08-11 | < 10.0.26200.9106 |
50 von 2,371 angezeigt