CVE-2017-8501

What it is

Microsoft Office allows a remote code execution vulnerability due to the way that it handles objects in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8502.

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

22.5% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2017-07-11 21:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:26 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 22.5% in the next 30 days (EPSS).
• Severity: 7.8 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2017-07-11 21:29 UTC

Last modified

2026-06-17 01:26 UTC

Exploit probability

22.5% · EPSS, next 30 days

Weakness

CWE-119 · Buffer errors

Record status

Modified

Affected

• Microsoft Excel 2007
• Microsoft Excel 2010
• Microsoft Excel 2013
• Microsoft Excel 2016
• Microsoft Excel Viewer 2007
• Microsoft Office 2011
• Microsoft Office 2016
• Microsoft Office Compatibility Pack

Attack profile CVSS 3.0 · 7.8

Attack vector

Local

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2017-8501.md and follow it. Check whether this project is affected by CVE-2017-8501. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge