Affects Microsoft Office — widely used enterprise software. Local code execution via crafted documents can enable malware, data theft, and broad disruption.
CVE-2026-70130
Heap-based buffer overflow in Microsoft Office allows local code execution via crafted documents.
Is CVE-2026-70130 being exploited?
Not confirmed. CVE-2026-70130 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.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-70130?
CVE-2026-70130 is rated High with a CVSS score of 8.4. 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-70130?
Yes. A fix has been recorded for CVE-2026-70130. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70130 affect?
CVE-2026-70130 affects Microsoft Office (Windows desktop). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70130?
Apply vendor updates when released; block/sandbox untrusted docs and enable Protected View.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local arbitrary code execution when a user opens a crafted Office file; can install malware, steal data, or maintain persistence under user context.
Immediate action required
- affected>= 16.0.1 and < https://aka.ms/OfficeSecurityReleases
- 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.