CWE Statistics for Microsoft Corporation as of 05/16/2026
3757
40
40
35
Reference
0-69.9%
|
|
Provider |
87.5
Contributor
70-94.9%
Provider
95-100%
| CVE | CNA Value | Alignment | NIST Value | Reason |
|---|---|---|---|---|
| CVE-2025-53732 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2025-53737 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2025-53741 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2025-55335 (2 of 2) | CWE-416 | CWE-416 | ||
| CWE-362 | More specific CWE option available | |||
| CVE-2025-55687 (2 of 2) | CWE-362 | CWE-362 | ||
| CWE-416 | More specific CWE option available | |||
| CVE-2025-59195 (2 of 2) | CWE-362 | CWE-362 | ||
| CWE-416 | More specific CWE option available | |||
| CVE-2025-59196 (2 of 2) | CWE-362 | CWE-362 | ||
| CWE-416 | More specific CWE option available | |||
| CVE-2025-59282 (2 of 2) | CWE-362 | CWE-362 | ||
| CWE-416 | More specific CWE option available | |||
| CVE-2025-62219 (2 of 2) | CWE-415 | CWE-415 | ||
| CWE-362 | More specific CWE option available | |||
| CVE-2025-62222 (2 of 2) | CWE-77 | CWE-77 | ||
| CWE-20 | More specific CWE option available | |||
| CVE-2025-62550 (2 of 2) | CWE-787 | CWE-787 | ||
| CWE-131 | More specific CWE option available | |||
| CVE-2025-62573 (2 of 2) | CWE-416 | CWE-416 | ||
| CWE-362 | More specific CWE option available | |||
|
CVE-2025-64657
(1 of 1)
|
CWE-787 | CWE-787 | ||
| CVE-2026-20960 (0 of 1) | CWE-285 | ≠ | CWE-863 | More specific CWE option available |
| CVE-2026-21236 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2026-21237 (2 of 2) | CWE-362 | CWE-362 | ||
| CWE-416 | More specific CWE option available | |||
| CVE-2026-21239 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2026-21244 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2026-21245 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2026-21246 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2026-21248 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2026-21256 (2 of 2) | CWE-77 | CWE-77 | ||
| CWE-94 | More specific CWE option available | |||
| CVE-2026-21259 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2026-21528 (1 of 1) | CWE-1327 | CWE-668 | ||
| CVE-2026-23665 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2026-26108 (1 of 1) | CWE-122 | CWE-787 | ||
| CVE-2026-26111 (2 of 2) | CWE-190 | CWE-190 | ||
| CWE-122 | More specific CWE option available | |||
| CVE-2026-26121 (2 of 2) | CWE-918 | CWE-918 | ||
| CWE-20 | More specific CWE option available | |||
| CVE-2026-26124 (1 of 1) | CWE-35 | CWE-22 | More specific CWE option available | |
|
CVE-2026-26133
(1 of 1)
|
CWE-77 | CWE-77 | ||
| CVE-2026-26134 (2 of 2) | CWE-190 | CWE-190 | ||
| CWE-416 | More specific CWE option available | |||
| CVE-2026-26141 (0 of 1) | CWE-287 | ≠ | CWE-863 | More specific CWE option available |
| CVE-2026-32173 (0 of 1) | CWE-287 | ≠ | CWE-863 | More specific CWE option available |
| CVE-2026-32213 (0 of 1) | CWE-285 | ≠ | CWE-863 | More specific CWE option available |
| CVE-2026-33105 (0 of 1) | CWE-285 | ≠ | CWE-863 | More specific CWE option available |
| CVE-2026-41107 (1 of 1) | CWE-73 | CWE-610 | ||
| CVE-2026-41610 (3 of 3) | CWE-79 | CWE-79 | ||
| CWE-200 | More specific CWE option available | |||
| CWE-59 | More specific CWE option available | |||
| CVE-2026-41611 (2 of 2) | CWE-80 | CWE-79 | ||
| CWE-77 | More specific CWE option available | |||
| CVE-2026-41612 (2 of 2) | CWE-22 | CWE-22 | ||
| CWE-23 | CWE-22 | |||
| CVE-2026-41613 (2 of 2) | CWE-384 | CWE-384 | ||
| CWE-78 | More specific CWE option available |