| CVE-2024-38475US | critical9.1OT critical | 100.0% (100th) | KEV | ✓9.0 SP-3 (93.M3.14.86) | 2024-07-01 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2025-29824US | —OT critical | 19.3% (97th) | KEV | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2024-38472US | — | 69.5% (99th) | Exploit | ✓9.0 SP-3 (93.M3.14.86) | 2024-07-01 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2024-38476US | critical9.8 | 41.6% (99th) | Exploit | ✓9.0 SP-3 (93.M3.14.86) | 2024-07-01 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2024-38473US | — | 25.9% (98th) | Exploit | ✓9.0 SP-3 (93.M3.14.86) | 2024-07-01 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2025-21204US | — | 7.00% (94th) | Exploit | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2024-40725US | medium5.3 | 4.42% (91st) | Exploit | ✓9.0 SP-3 (93.M3.14.86) | 2024-07-18 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2023-38709US | — | 3.91% (90th) | Exploit | ✓9.0 SP-3 (93.M3.14.86) | 2024-04-04 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2025-29810US | — | 2.57% (85th) | Exploit | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2024-39573US | — | 35.4% (98th) | — | ✓9.0 SP-3 (93.M3.14.86) | 2024-07-01 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2025-26670US | — | 11.1% (96th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-29809US | — | 4.17% (91st) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27738US | — | 3.50% (89th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-21197US | — | 3.25% (88th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2024-38477US | high7.5 | 3.15% (88th) | — | ✓9.0 SP-3 (93.M3.14.86) | 2024-07-01 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2024-38474US | critical9.8 | 2.46% (84th) | — | ✓9.0 SP-3 (93.M3.14.86) | 2024-07-01 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2025-9231US | — | 2.24% (83rd) | — | ✓9.0 SP-3 (93.M3.14.86) | 2025-09-30 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2025-26641US | — | 2.23% (83rd) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-9232US | — | 2.00% (81st) | — | ✓9.0 SP-3 (93.M3.14.86) | 2025-09-30 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2025-26672US | — | 1.82% (79th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-26663US | — | 1.75% (78th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2024-36387US | — | 1.71% (77th) | — | ✓9.0 SP-3 (93.M3.14.86) | 2024-07-01 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2025-27477US | — | 1.57% (75th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-26669US | — | 1.50% (74th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27487US | — | 1.49% (74th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27491US | — | 1.40% (72nd) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-21222US | — | 1.36% (72nd) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-21221US | — | 1.36% (72nd) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-21205US | — | 1.36% (72nd) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27481US | — | 1.24% (69th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-26668US | — | 1.23% (69th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27727US | — | 1.02% (63rd) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27736US | — | 0.92% (60th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2024-39884US | — | 0.89% (59th) | — | ✓9.0 SP-3 (93.M3.14.86) | 2024-07-04 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2025-27742US | — | 0.86% (58th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-26637US | — | 0.84% (58th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-59775US | — | 0.82% (57th) | — | ✓9.0 SP-3 (93.M3.14.86) | 2025-12-05 | < 9.0 SP-3 (93.M3.14.86) |
| CVE-2025-27484US | — | 0.81% (57th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27741US | — | 0.80% (56th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27737US | — | 0.76% (55th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27483US | — | 0.76% (55th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27733US | — | 0.73% (54th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-24073US | — | 0.60% (48th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2024-47557US | critical9.8 | 0.52% (44th) | — | ✗no fix | 2024-10-07 | ≤ Core <7.0.11 |
| CVE-2024-47556US | critical9.8 | 0.52% (44th) | — | ✗no fix | 2024-10-07 | ≤ Core <7.0.11 |
| CVE-2024-47559US | high8.8 | 0.50% (43rd) | — | ✗no fix | 2024-10-07 | ≤ Core <7.0.11 |
| CVE-2024-47558US | high8.8 | 0.50% (43rd) | — | ✗no fix | 2024-10-07 | ≤ Core <7.0.11 |
| CVE-2025-26648US | — | 0.47% (41st) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27478US | — | 0.45% (39th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |
| CVE-2025-27735US | —OT elevated | 0.40% (34th) | — | ✗no fix | 2025-04-08 | ≤ v2 for Windows 10 <April 2025 Security Patch Update |