| CVE-2026-21514US | —OT critical | 1.59% (75th) | KEV | ✓https://aka.ms/OfficeSecurityReleases | 2026-02-10 | 2 versions |
| CVE-2025-27751US | — | 2.48% (85th) | Exploit | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-47175US | — | 2.39% (84th) | Exploit | ✓https://aka.ms/OfficeSecurityReleases | 2025-06-10 | 2 versions |
| CVE-2025-47165US | — | 2.19% (82nd) | Exploit | ✓https://aka.ms/OfficeSecurityReleases | 2025-06-10 | 2 versions |
| CVE-2025-47171US | — | 1.68% (77th) | Exploit | ✓https://aka.ms/OfficeSecurityReleases | 2025-06-10 | 2 versions |
| CVE-2025-47957US | — | 1.31% (71st) | Exploit | ✓https://aka.ms/OfficeSecurityReleases | 2025-06-10 | 2 versions |
| CVE-2025-47176US | — | 0.75% (55th) | Exploit | ✓https://aka.ms/OfficeSecurityReleases | 2025-06-10 | 2 versions |
| CVE-2024-43504US | — | 6.50% (94th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-10-08 | 2 versions |
| CVE-2026-21511US | — | 3.97% (90th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2026-02-10 | 2 versions |
| CVE-2025-47994US | high8.6 | 3.28% (88th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-07-08 | 2 versions |
| CVE-2024-49033US | — | 2.14% (82nd) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-11-12 | 2 versions |
| CVE-2024-43609US | medium6.5 | 2.13% (82nd) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-10-08 | 2 versions |
| CVE-2026-21260US | — | 1.52% (74th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2026-02-10 | 2 versions |
| CVE-2024-49069US | — | 1.17% (67th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-12-12 | 2 versions |
| CVE-2025-29792US | — | 1.14% (66th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-21381US | — | 1.14% (66th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-02-11 | 2 versions |
| CVE-2024-49065US | — | 1.10% (66th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-12-12 | 2 versions |
| CVE-2024-49142US | — | 1.10% (65th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-12-12 | 2 versions |
| CVE-2025-27749US | — | 1.08% (65th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-27748US | — | 1.08% (65th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-27745US | — | 1.08% (65th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-29791US | — | 1.04% (64th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-27752US | — | 1.04% (64th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-21383US | medium5.5 | 1.01% (63rd) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-02-11 | 2 versions |
| CVE-2024-49026US | — | 0.96% (61st) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-11-12 | 2 versions |
| CVE-2025-21387US | — | 0.93% (61st) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-02-11 | 2 versions |
| CVE-2025-27750US | — | 0.86% (58th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-27746US | — | 0.86% (58th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2024-49032US | — | 0.86% (58th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-11-12 | 2 versions |
| CVE-2025-21394US | — | 0.84% (58th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-02-11 | 2 versions |
| CVE-2025-21392US | — | 0.84% (58th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-02-11 | 2 versions |
| CVE-2025-21390US | — | 0.84% (58th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-02-11 | 2 versions |
| CVE-2025-21386US | — | 0.84% (58th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-02-11 | 2 versions |
| CVE-2025-27747US | — | 0.82% (57th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-29822US | — | 0.82% (57th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-62199US | — | 0.81% (57th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-11-11 | 2 versions |
| CVE-2025-62562US | — | 0.81% (57th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-12-09 | 2 versions |
| CVE-2025-26642US | — | 0.80% (56th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-21397US | — | 0.78% (56th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-02-11 | 2 versions |
| CVE-2024-43616US | — | 0.77% (56th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-10-08 | 2 versions |
| CVE-2025-60728US | medium4.3 | 0.77% (55th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-11-11 | 2 versions |
| CVE-2025-49703US | — | 0.77% (55th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-07-08 | 2 versions |
| CVE-2024-49031US | — | 0.77% (55th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-11-12 | 2 versions |
| CVE-2024-49030US | — | 0.77% (55th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-11-12 | 2 versions |
| CVE-2024-49029US | — | 0.77% (55th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-11-12 | 2 versions |
| CVE-2024-49028US | — | 0.77% (55th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-11-12 | 2 versions |
| CVE-2024-49027US | — | 0.77% (55th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-11-12 | 2 versions |
| CVE-2025-29820US | — | 0.77% (55th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-04-08 | 2 versions |
| CVE-2025-47162US | — | 0.76% (55th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2025-06-10 | 2 versions |
| CVE-2024-43505US | — | 0.75% (55th) | — | ✓https://aka.ms/OfficeSecurityReleases | 2024-10-08 | 2 versions |