Affects Microsoft Office Excel — a ubiquitous enterprise app. RCE via crafted files can cause widespread disruption and malware spread.
CVE-2026-62870
Use-after-free in Excel allows remote code execution via crafted spreadsheet.
Is CVE-2026-62870 being exploited?
Not confirmed. CVE-2026-62870 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.63% probability of exploitation in the next 30 days.
How severe is CVE-2026-62870?
CVE-2026-62870 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62870?
Yes. A fix has been recorded for CVE-2026-62870. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62870 affect?
CVE-2026-62870 affects Microsoft Excel (Office). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62870?
Apply vendor patch when released; block/scan Excel attachments and enable Protected View/macros restrictions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via a crafted Excel file; attacker can run arbitrary code, deploy malware, or take control of affected hosts.
Immediate action required
- affected>= 16.0.1 and < https://aka.ms/OfficeSecurityReleases
- affected>= 16.0.0.0 and < 16.0.5561.1001
- affected>= 19.0.0 and < https://aka.ms/OfficeSecurityReleases
- affected>= 16.0.1 and < https://aka.ms/OfficeSecurityReleases
- affected>= 16.0.0 and < https://aka.ms/OfficeSecurityReleases
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.