| CVE-2025-49704US | —OT critical | 100.0% (100th) | KEV | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-49706US | —OT critical | 99.1% (100th) | KEV | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-27751US | — | 2.48% (85th) | Exploit | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-53783US | — | 0.81% (57th) | Exploit | ✗no fix | 2025-08-12 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-29793US | — | 23.6% (98th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-49712US | — | 20.7% (98th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-53760US | — | 18.9% (97th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-53766US | — | 8.19% (95th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-29794US | — | 4.76% (92nd) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-47994US | high8.6 | 3.28% (88th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-49701US | — | 1.29% (70th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-27744US | — | 1.20% (68th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2024-49069US | — | 1.17% (67th) | — | ✗no fix | 2024-12-12 | — |
| CVE-2025-26687US | — | 1.14% (66th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-29792US | — | 1.14% (66th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2024-49142US | — | 1.10% (65th) | — | ✗no fix | 2024-12-12 | — |
| CVE-2025-27749US | — | 1.08% (65th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27748US | — | 1.08% (65th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27745US | — | 1.08% (65th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-29801US | —OT elevated | 1.06% (65th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-29800US | — | 1.06% (65th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-29791US | — | 1.04% (64th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27752US | — | 1.04% (64th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-26630US | — | 0.97% (62nd) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-24057US | — | 0.97% (62nd) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-27750US | — | 0.86% (58th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27746US | — | 0.86% (58th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27747US | — | 0.82% (57th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-29822US | — | 0.82% (57th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-26642US | — | 0.80% (56th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-49703US | — | 0.77% (55th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-29820US | — | 0.77% (55th) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-24082US | — | 0.71% (53rd) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-24083US | — | 0.70% (53rd) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-24081US | — | 0.70% (53rd) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-24080US | — | 0.70% (53rd) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-24079US | — | 0.70% (53rd) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-24075US | — | 0.69% (53rd) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-49695US | — | 0.69% (53rd) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-29823US | — | 0.69% (52nd) | — | ✗no fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-49702US | — | 0.66% (51st) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-49698US | — | 0.65% (51st) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-49696US | — | 0.64% (50th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-48812US | — | 0.61% (49th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-24077US | — | 0.59% (48th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-26629US | — | 0.58% (47th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-24078US | — | 0.57% (47th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-53740US | — | 0.57% (47th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-53731US | — | 0.57% (47th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |
| CVE-2025-53739US | — | 0.56% (46th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/16.0.1|<https://aka.ms/officesecurityreleases |