| 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.14393.9060 | 2026-04-14 | 3 Versionen |
| CVE-2026-32202US | —OT kritisch | 70.9% (99th) | KEV | ✓10.0.14393.9339 | 2026-04-14 | 3 Versionen |
| CVE-2025-24054US | medium5.4OT kritisch | 62.3% (99th) | KEV | ✓10.0.14393.7876 | 2025-03-11 | 2 Versionen |
| CVE-2026-21510US | —OT kritisch | 61.2% (99th) | KEV | ✗kein Fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2025-26633US | —OT kritisch | 30.4% (98th) | KEV | ✓10.0.14393.7876 | 2025-03-11 | 2 Versionen |
| CVE-2026-20805US | —OT kritisch | 7.46% (94th) | KEV | ✓10.0.14393.8783 | 2026-01-13 | 3 Versionen |
| CVE-2025-60710US | —OT kritisch | 4.61% (92nd) | KEV | ✗kein Fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2025-62215US | —OT kritisch | 4.46% (91st) | KEV | ✗kein Fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2026-21533US | —OT kritisch | 4.15% (91st) | KEV | ✗kein Fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2025-24985US | —OT kritisch | 3.89% (90th) | KEV | ✓10.0.14393.7876 | 2025-03-11 | 2 Versionen |
| CVE-2025-62221US | —OT kritisch | 2.50% (85th) | KEV | ✗kein Fix | 2025-12-09 | ≤ vers:unknown/* |
| CVE-2026-81963US | high7.8OT kritisch | 0.39% (33rd) | KEV | ✗kein Fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2026-68820US | —OT kritisch | 0.33% (26th) | KEV | ✓10.0.14393.9418 | 2026-08-11 | 3 Versionen |
| CVE-2026-21513US | —OT kritisch | 15.9% (97th) | KEV | ✗kein Fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-96951US | high8.8OT kritisch | 9.81% (96th) | KEV | ✓10.0.14393.9612 | 2026-10-13 | 2 Versionen |
| CVE-2026-21525US | —OT kritisch | 4.87% (92nd) | KEV | ✗kein Fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2025-59230US | —OT kritisch | 2.66% (86th) | KEV | ✓10.0.14393.8519 | 2025-10-14 | 2 Versionen |
| CVE-2026-21519US | —OT kritisch | 2.48% (84th) | KEV | ✗kein Fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2025-24993US | —OT kritisch | 2.22% (83rd) | KEV | ✓10.0.14393.7876 | 2025-03-11 | 2 Versionen |
| CVE-2025-24991US | —OT kritisch | 2.02% (81st) | KEV | ✓10.0.14393.7876 | 2025-03-11 | 2 Versionen |
| CVE-2025-24984US | —OT kritisch | 1.99% (81st) | KEV | ✓10.0.14393.7876 | 2025-03-11 | 2 Versionen |
| CVE-2025-24983US | —OT kritisch | 1.87% (79th) | KEV | ✓10.0.14393.7876 | 2025-03-11 | 2 Versionen |
| CVE-2026-85880US | high7.8OT kritisch | 0.39% (33rd) | KEV | ✓10.0.14393.9512 | 2026-09-08 | 3 Versionen |
| CVE-2026-56155US | —OT kritisch | 0.35% (28th) | KEV | ✓10.0.14393.9339 | 2026-07-14 | 2 Versionen |
| CVE-2026-41089US | — | 79.6% (100th) | Exploit | ✗kein Fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2025-21298US | — | 74.4% (99th) | Exploit | ✓10.0.14393.7699 | 2025-01-14 | 2 Versionen |
| CVE-2026-49160US | — | 56.6% (99th) | Exploit | ✓10.0.14393.9234 | 2026-06-09 | 3 Versionen |
| CVE-2025-54918US | — | 25.3% (98th) | Exploit | ✓10.0.14393.8422 | 2025-09-09 | 2 Versionen |
| CVE-2025-24071US | — | 23.3% (98th) | Exploit | ✓10.0.14393.7876 | 2025-03-11 | 2 Versionen |
| CVE-2025-55234US | critical9.8 | 20.6% (98th) | Exploit | ✓10.0.14393.8422 | 2025-09-09 | 2 Versionen |
| CVE-2025-21293US | — | 15.0% (97th) | Exploit | ✓10.0.14393.7699 | 2025-01-14 | 2 Versionen |
| CVE-2026-20841US | — | 9.01% (95th) | Exploit | ✗kein Fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-42980US | — | 6.95% (94th) | Exploit | ✓10.0.14393.9234 | 2026-06-09 | 3 Versionen |
| CVE-2026-20817US | — | 5.42% (93rd) | Exploit | ✗kein Fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2026-50507US | —OT erhöht | 5.02% (92nd) | Exploit | ✓10.0.14393.9234 | 2026-06-09 | 3 Versionen |
| CVE-2026-24294US | — | 4.85% (92nd) | Exploit | ✓10.0.14393.8957 | 2026-03-10 | 3 Versionen |
| CVE-2026-40369US | — | 4.72% (92nd) | Exploit | ✗kein Fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2025-54110US | — | 4.72% (92nd) | Exploit | ✓10.0.14393.8422 | 2025-09-09 | 2 Versionen |
| CVE-2026-33829US | — | 3.51% (89th) | Exploit | ✓10.0.14393.9060 | 2026-04-14 | 3 Versionen |
| CVE-2026-24291US | — | 3.30% (88th) | Exploit | ✓10.0.14393.8957 | 2026-03-10 | 3 Versionen |
| CVE-2026-20929US | — | 2.87% (87th) | Exploit | ✓10.0.14393.8783 | 2026-01-13 | 3 Versionen |
| CVE-2026-41096US | — | 2.70% (86th) | Exploit | ✗kein Fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2026-20820US | — | 2.56% (85th) | Exploit | ✓10.0.14393.8783 | 2026-01-13 | 3 Versionen |
| CVE-2025-62454US | — | 2.29% (83rd) | Exploit | ✗kein Fix | 2025-12-09 | ≤ vers:unknown/* |
| CVE-2025-60719US | — | 1.93% (80th) | Exploit | ✗kein Fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2025-24035US | — | 1.72% (77th) | Exploit | ✓10.0.14393.7876 | 2025-03-11 | 2 Versionen |
| CVE-2026-21248US | — | 1.33% (71st) | Exploit | ✗kein Fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-21244US | — | 1.33% (71st) | Exploit | ✗kein Fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-25177US | — | 1.31% (70th) | Exploit | ✓10.0.14393.8957 | 2026-03-10 | 3 Versionen |
| CVE-2025-59254US | — | 1.11% (66th) | Exploit | ✓10.0.14393.8519 | 2025-10-14 | 2 Versionen |
50 von 2,579 angezeigt