Widely used Microsoft Office; high-risk local code execution via untrusted pointer dereference.
CVE-2026-26113
Office local code execution via untrusted pointer dereference.
Is CVE-2026-26113 being exploited?
Not confirmed. CVE-2026-26113 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.54% probability of exploitation in the next 30 days.
How severe is CVE-2026-26113?
CVE-2026-26113 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-26113?
Yes. A fix has been recorded for CVE-2026-26113. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-26113 affect?
CVE-2026-26113 affects Microsoft Office. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-26113?
Apply latest Office updates when available; enable automatic updates.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local code execution on Windows; attacker with local access can run arbitrary code on affected hosts.
Patch when possible
- affected>= 16.0.1 and < https://aka.ms/OfficeSecurityReleases
- affected>= 16.0.0 and < 16.0.5543.1000
- 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
- affected>= 16.0.1 and < 16.107.26030819
- affected>= 16.0.0 and < 16.107.26030819
- affected>= 16.0.0 and < 16.0.5543.1000
- affected>= 16.0.0 and < 16.0.10417.20102
- affected>= 16.0.0 and < 16.0.19725.20076
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.