Excel vulnerabilities: known CVEs & security history
Microsoft · Actively exploited · 111 tracked CVEs · 1 actively exploited · updated September 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Excel release lines — 111 in total, with 1 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Excel's current status and the safe version to run.
Known Excel CVEs
Actively-exploited and most-severe first. Showing the top 80 of 111. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2021-42292⚡ exploited | high | 7.8 | 32% | 2021 |
| CVE-2026-78518 | high | 8.8 | — | 2026 |
| CVE-2026-65807 | high | 8.8 | 0% | 2026 |
| CVE-2026-62870 | high | 8.8 | 1% | 2026 |
| CVE-2022-41106 | high | 8.8 | 2% | 2022 |
| CVE-2026-44822 | high | 8.2 | 1% | 2026 |
| CVE-2026-81960 | high | 7.8 | 0% | 2026 |
| CVE-2026-81959 | high | 7.8 | 0% | 2026 |
| CVE-2026-81957 | high | 7.8 | 0% | 2026 |
| CVE-2026-81956 | high | 7.8 | 0% | 2026 |
| CVE-2026-81954 | high | 7.8 | 0% | 2026 |
| CVE-2026-81953 | high | 7.8 | 0% | 2026 |
| CVE-2026-81951 | high | 7.8 | 0% | 2026 |
| CVE-2026-81950 | high | 7.8 | 0% | 2026 |
| CVE-2026-81949 | high | 7.8 | 0% | 2026 |
| CVE-2026-81948 | high | 7.8 | 0% | 2026 |
| CVE-2026-81947 | high | 7.8 | 0% | 2026 |
| CVE-2026-81398 | high | 7.8 | 0% | 2026 |
| CVE-2026-81397 | high | 7.8 | 0% | 2026 |
| CVE-2026-81396 | high | 7.8 | 0% | 2026 |
| CVE-2026-81388 | high | 7.8 | — | 2026 |
| CVE-2026-81386 | high | 7.8 | — | 2026 |
| CVE-2026-68817 | high | 7.8 | 0% | 2026 |
| CVE-2026-68816 | high | 7.8 | 0% | 2026 |
| CVE-2026-68815 | high | 7.8 | 0% | 2026 |
| CVE-2026-68814 | high | 7.8 | 0% | 2026 |
| CVE-2026-68812 | high | 7.8 | 0% | 2026 |
| CVE-2026-68811 | high | 7.8 | 0% | 2026 |
| CVE-2026-68810 | high | 7.8 | 0% | 2026 |
| CVE-2026-68807 | high | 7.8 | 0% | 2026 |
| CVE-2026-68806 | high | 7.8 | 0% | 2026 |
| CVE-2026-68805 | high | 7.8 | 0% | 2026 |
| CVE-2026-68804 | high | 7.8 | 0% | 2026 |
| CVE-2026-68803 | high | 7.8 | 0% | 2026 |
| CVE-2026-68801 | high | 7.8 | 0% | 2026 |
| CVE-2026-68800 | high | 7.8 | 0% | 2026 |
| CVE-2026-68796 | high | 7.8 | 0% | 2026 |
| CVE-2026-68795 | high | 7.8 | 0% | 2026 |
| CVE-2026-68794 | high | 7.8 | 0% | 2026 |
| CVE-2026-68793 | high | 7.8 | 0% | 2026 |
| CVE-2026-55949 | high | 7.8 | 0% | 2026 |
| CVE-2026-55947 | high | 7.8 | 0% | 2026 |
| CVE-2026-55141 | high | 7.8 | 0% | 2026 |
| CVE-2026-55137 | high | 7.8 | 0% | 2026 |
| CVE-2026-55136 | high | 7.8 | 0% | 2026 |
| CVE-2026-55131 | high | 7.8 | 0% | 2026 |
| CVE-2026-55058 | high | 7.8 | 0% | 2026 |
| CVE-2026-55053 | high | 7.8 | 0% | 2026 |
| CVE-2026-55048 | high | 7.8 | 0% | 2026 |
| CVE-2026-55044 | high | 7.8 | 0% | 2026 |
| CVE-2026-55041 | high | 7.8 | 0% | 2026 |
| CVE-2026-55039 | high | 7.8 | 0% | 2026 |
| CVE-2026-55037 | high | 7.8 | 0% | 2026 |
| CVE-2026-55036 | high | 7.8 | 0% | 2026 |
| CVE-2026-55031 | high | 7.8 | 0% | 2026 |
| CVE-2026-55029 | high | 7.8 | 0% | 2026 |
| CVE-2026-55025 | high | 7.8 | 0% | 2026 |
| CVE-2026-55024 | high | 7.8 | 0% | 2026 |
| CVE-2026-58618 | high | 7.8 | 0% | 2026 |
| CVE-2026-55948 | high | 7.8 | 0% | 2026 |
| CVE-2026-55899 | high | 7.8 | 0% | 2026 |
| CVE-2026-50675 | high | 7.8 | 0% | 2026 |
| CVE-2026-45469 | high | 7.8 | 0% | 2026 |
| CVE-2026-44823 | high | 7.8 | 0% | 2026 |
| CVE-2026-44820 | high | 7.8 | 0% | 2026 |
| CVE-2026-44817 | high | 7.8 | 0% | 2026 |
| CVE-2026-44812 | high | 7.8 | 0% | 2026 |
| CVE-2026-44803 | high | 7.8 | 0% | 2026 |
| CVE-2024-43465 | high | 7.8 | 1% | 2024 |
| CVE-2024-20673 | high | 7.8 | 1% | 2024 |
| CVE-2022-41063 | high | 7.8 | 1% | 2022 |
| CVE-2021-40442 | high | 7.8 | 2% | 2021 |
| CVE-2021-38660 | high | 7.8 | 2% | 2021 |
| CVE-2021-38655 | high | 7.8 | 5% | 2021 |
| CVE-2021-34518 | high | 7.8 | 2% | 2021 |
| CVE-2021-34501 | high | 7.8 | 53% | 2021 |
| CVE-2021-27057 | high | 7.8 | 3% | 2021 |
| CVE-2021-27054 | high | 7.8 | 3% | 2021 |
| CVE-2021-27053 | high | 7.8 | 4% | 2021 |
| CVE-2026-55122 | high | 7.1 | 0% | 2026 |
31 older / lower-severity CVEs not shown — see Excel's full record.
Is my Excel 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 Excel version → · Monitor Excel for new CVEs →
Excel vulnerabilities — frequently asked
How many known vulnerabilities does Excel have?
IsItPatched tracks 111 CVEs for Excel, 1 of which is actively exploited (CISA KEV). 0 are critical-severity and 83 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Excel have any actively-exploited vulnerabilities?
Yes — 1 Excel CVE is in CISA's Known Exploited Vulnerabilities catalog, meaning it is confirmed exploited in the wild. Patch it as a priority.
What is the most severe Excel vulnerability?
Among tracked issues, CVE-2021-42292 (HIGH, CVSS 7.8), which is actively exploited, ranks highest.
Is Excel safe to use?
It depends on the version. The latest supported Excel 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: Excel security status · Excel end-of-life · actively-exploited CVEs. Always verify against Microsoft's advisories — see our disclaimer.