Microsoft Office vulnerabilities: known CVEs & security history
Microsoft · Office / Productivity · 147 tracked CVEs · 5 actively exploited · updated November 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Microsoft Office release lines — 147 in total, with 5 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Microsoft Office's current status and the safe version to run.
Known Microsoft Office CVEs
Actively-exploited and most-severe first. Showing the top 80 of 147. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2023-35311⚡ exploited | high | 8.8 | 16% | 2023 |
| CVE-2026-21509⚡ exploited | high | 7.8 | 72% | 2026 |
| CVE-2021-42292⚡ exploited | high | 7.8 | 32% | 2021 |
| CVE-2021-38646⚡ exploited | high | 7.8 | 4% | 2021 |
| CVE-2021-27059⚡ exploited | high | 7.6 | 3% | 2021 |
| CVE-2023-21716 | critical | 9.8 | 82% | 2023 |
| CVE-2020-0901 | critical | 9.8 | 12% | 2020 |
| CVE-2015-6093 | high | 9.3 | 23% | 2015 |
| CVE-2015-2477 | high | 9.3 | 14% | 2015 |
| CVE-2015-2470 | high | 9.3 | 27% | 2015 |
| CVE-2015-2469 | high | 9.3 | 27% | 2015 |
| CVE-2015-2468 | high | 9.3 | 43% | 2015 |
| CVE-2015-2467 | high | 9.3 | 28% | 2015 |
| CVE-2015-2466 | high | 9.3 | 17% | 2015 |
| CVE-2015-1683 | high | 9.3 | 14% | 2015 |
| CVE-2015-0085 | high | 9.3 | 19% | 2015 |
| CVE-2012-2524 | high | 9.3 | 20% | 2012 |
| CVE-2006-0033 | high | 9.3 | 15% | 2006 |
| CVE-2006-1316 | high | 9.3 | 15% | 2006 |
| CVE-2006-2389 | high | 9.3 | 39% | 2006 |
| CVE-2026-40420 | high | 8.8 | 0% | 2026 |
| CVE-2026-35436 | high | 8.8 | 0% | 2026 |
| CVE-2024-30103 | high | 8.8 | 3% | 2024 |
| CVE-2024-21378 | high | 8.8 | 11% | 2024 |
| CVE-2022-41106 | high | 8.8 | 2% | 2022 |
| CVE-2018-0851 | high | 8.8 | 19% | 2018 |
| CVE-2017-8512 | high | 8.8 | 22% | 2017 |
| CVE-2017-8509 | high | 8.8 | 18% | 2017 |
| CVE-2026-40367 | high | 8.4 | 0% | 2026 |
| CVE-2026-40366 | high | 8.4 | 0% | 2026 |
| CVE-2026-40364 | high | 8.4 | 4% | 2026 |
| CVE-2026-40363 | high | 8.4 | 0% | 2026 |
| CVE-2026-40361 | high | 8.4 | 1% | 2026 |
| CVE-2026-40358 | high | 8.4 | 0% | 2026 |
| CVE-2026-32190 | high | 8.4 | 0% | 2026 |
| CVE-2025-62557 | high | 8.4 | 0% | 2025 |
| CVE-2025-62554 | high | 8.4 | 0% | 2025 |
| CVE-2025-59236 | high | 8.4 | 0% | 2025 |
| CVE-2025-54910 | high | 8.4 | 1% | 2025 |
| CVE-2021-34469 | high | 8.2 | 3% | 2021 |
| CVE-2023-36897 | high | 8.1 | 2% | 2023 |
| CVE-2026-55130 | high | 7.8 | 0% | 2026 |
| CVE-2026-55120 | high | 7.8 | 0% | 2026 |
| CVE-2026-42831 | high | 7.8 | 0% | 2026 |
| CVE-2026-40419 | high | 7.8 | 0% | 2026 |
| CVE-2026-40418 | high | 7.8 | 0% | 2026 |
| CVE-2026-40362 | high | 7.8 | 0% | 2026 |
| CVE-2026-40360 | high | 7.8 | 0% | 2026 |
| CVE-2026-40359 | high | 7.8 | 0% | 2026 |
| CVE-2026-32200 | high | 7.8 | 0% | 2026 |
| CVE-2026-32199 | high | 7.8 | 0% | 2026 |
| CVE-2026-32198 | high | 7.8 | 0% | 2026 |
| CVE-2026-32197 | high | 7.8 | 0% | 2026 |
| CVE-2026-32189 | high | 7.8 | 0% | 2026 |
| CVE-2025-62564 | high | 7.8 | 1% | 2025 |
| CVE-2025-62563 | high | 7.8 | 1% | 2025 |
| CVE-2025-62561 | high | 7.8 | 1% | 2025 |
| CVE-2025-62560 | high | 7.8 | 1% | 2025 |
| CVE-2025-62556 | high | 7.8 | 1% | 2025 |
| CVE-2025-62553 | high | 7.8 | 1% | 2025 |
| CVE-2025-62552 | high | 7.8 | 1% | 2025 |
| CVE-2025-62203 | high | 7.8 | 1% | 2025 |
| CVE-2025-62201 | high | 7.8 | 1% | 2025 |
| CVE-2025-62200 | high | 7.8 | 1% | 2025 |
| CVE-2025-60727 | high | 7.8 | 1% | 2025 |
| CVE-2025-59238 | high | 7.8 | 0% | 2025 |
| CVE-2025-59234 | high | 7.8 | 1% | 2025 |
| CVE-2025-59233 | high | 7.8 | 1% | 2025 |
| CVE-2025-59231 | high | 7.8 | 1% | 2025 |
| CVE-2025-59227 | high | 7.8 | 1% | 2025 |
| CVE-2025-59225 | high | 7.8 | 0% | 2025 |
| CVE-2025-59224 | high | 7.8 | 0% | 2025 |
| CVE-2025-59223 | high | 7.8 | 0% | 2025 |
| CVE-2025-54908 | high | 7.8 | 1% | 2025 |
| CVE-2025-54907 | high | 7.8 | 1% | 2025 |
| CVE-2025-54904 | high | 7.8 | 1% | 2025 |
| CVE-2025-54903 | high | 7.8 | 1% | 2025 |
| CVE-2025-54902 | high | 7.8 | 1% | 2025 |
| CVE-2025-54900 | high | 7.8 | 1% | 2025 |
| CVE-2025-54899 | high | 7.8 | 1% | 2025 |
67 older / lower-severity CVEs not shown — see Microsoft Office's full record.
Is my Microsoft Office version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Microsoft Office version → · Monitor Microsoft Office for new CVEs →
Microsoft Office vulnerabilities — frequently asked
How many known vulnerabilities does Microsoft Office have?
IsItPatched tracks 147 CVEs for Microsoft Office, 5 of which are actively exploited (CISA KEV). 2 are critical-severity and 126 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Microsoft Office have any actively-exploited vulnerabilities?
Yes — 5 Microsoft Office CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (1 linked to ransomware). Patch these as a priority.
What is the most severe Microsoft Office vulnerability?
Among tracked issues, CVE-2023-35311 (HIGH, CVSS 8.8), which is actively exploited, ranks highest — a CWE-367 weakness.
Is Microsoft Office safe to use?
It depends on the version. The latest supported Microsoft Office release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Microsoft Office security status · Microsoft Office end-of-life · actively-exploited CVEs. Always verify against Microsoft's advisories — see our disclaimer.