| CVE-2025-59237US | — | 2.46% (84th) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59228US | — | 1.36% (72nd) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-21186US | — | 1.19% (68th) | — | ✓16.0.5483.1001 | 2025-01-14 | 16.0.0 → 16.0.5483.1001 |
| CVE-2025-21366US | — | 1.15% (67th) | — | ✓16.0.5483.1001 | 2025-01-14 | 16.0.0 → 16.0.5483.1001 |
| CVE-2025-21395US | — | 1.06% (64th) | — | ✓16.0.5487.1000 | 2025-01-14 | 16.0.0 → 16.0.5487.1000 |
| CVE-2025-26630US | — | 0.97% (62nd) | — | ✓16.0.5491.1001 | 2025-03-11 | 2 Versionen |
| CVE-2025-24057US | — | 0.97% (62nd) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.0|<16.0.5491.1001 |
| CVE-2025-26642US | — | 0.80% (56th) | — | ✓16.0.5495.1000 | 2025-04-08 | 16.0.0 → 16.0.5495.1000 |
| CVE-2025-24082US | — | 0.71% (53rd) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.0|<16.0.5491.1001 |
| CVE-2025-24083US | — | 0.70% (53rd) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.0|<16.0.5491.1001 |
| CVE-2025-24081US | — | 0.70% (53rd) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.0|<16.0.5491.1001 |
| CVE-2025-24080US | — | 0.70% (53rd) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.0|<16.0.5491.1001 |
| CVE-2025-24079US | — | 0.70% (53rd) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.0|<16.0.5491.1001 |
| CVE-2025-24075US | — | 0.69% (53rd) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.0|<16.0.5491.1001 |
| CVE-2025-59235US | — | 0.65% (51st) | — | ✓16.0.5522.1000 | 2025-10-14 | 2 Versionen |
| CVE-2025-59234US | — | 0.60% (48th) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-62552US | — | 0.60% (48th) | — | ✓16.0.5530.1000 | 2025-12-09 | 16.0.0 → 16.0.5530.1000 |
| CVE-2025-24077US | — | 0.59% (48th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.0|<16.0.5491.1001 |
| CVE-2025-26629US | — | 0.58% (47th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.0|<16.0.5491.1001 |
| CVE-2025-24078US | — | 0.57% (47th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.0|<16.0.5491.1001 |
| CVE-2025-59233US | — | 0.53% (44th) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59231US | — | 0.53% (44th) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59227US | — | 0.51% (43rd) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59232US | — | 0.48% (42nd) | — | ✓16.0.5522.1000 | 2025-10-14 | 2 Versionen |
| CVE-2026-64920US | — | 0.47% (40th) | — | ✓16.0.5565.1000 | 2026-08-11 | 16.0.0 → 16.0.5565.1000 |
| CVE-2026-64919US | — | 0.47% (40th) | — | ✓16.0.5565.1000 | 2026-08-11 | 16.0.0 → 16.0.5565.1000 |
| CVE-2026-64914US | — | 0.47% (40th) | — | ✓16.0.5565.1000 | 2026-08-11 | 16.0.0 → 16.0.5565.1000 |
| CVE-2026-64912US | — | 0.47% (40th) | — | ✓16.0.5565.1000 | 2026-08-11 | 16.0.0 → 16.0.5565.1000 |
| CVE-2026-64908US | — | 0.47% (40th) | — | ✓16.0.5565.1000 | 2026-08-11 | 16.0.0 → 16.0.5565.1000 |
| CVE-2026-64906US | — | 0.47% (40th) | — | ✓16.0.5565.1000 | 2026-08-11 | 16.0.0 → 16.0.5565.1000 |
| CVE-2025-59222US | — | 0.47% (40th) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59243US | — | 0.45% (39th) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59229US | — | 0.42% (36th) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59236US | high7.8 | 0.41% (35th) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59221US | — | 0.39% (33rd) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59238US | — | 0.38% (32nd) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59226US | — | 0.38% (32nd) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59225US | — | 0.38% (32nd) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59224US | — | 0.38% (32nd) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-59223US | — | 0.38% (32nd) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |