Vulnerability · CVE-2017-8509
A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability".
Published Jun 15, 2017 · catalog updated Oct 15, 2026 · A remote code execution
Check this week
CVE-2017-8509 is not in CISA KEV. FIRST estimates a 18.24% chance of exploitation in the next 30 days. Check whether you run A remote code execution.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (A remote code execution).
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High8.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 18.24%
- Remediation
- Advisory link
- Affected products
- cpe microsoft/office · cpe microsoft/office compatibility pack · cpe microsoft/office web apps · cpe microsoft/office web apps server · cpe microsoft/onenote
A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8510, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-8506.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe microsoft/office2007
- cpe microsoft/office2010
- cpe microsoft/office2013
- cpe microsoft/office2016
- cpe microsoft/office compatibility packversion unspecified
- cpe microsoft/office web apps2010
- cpe microsoft/office web apps server2013
- cpe microsoft/onenote2010
How to fix CVE-2017-8509
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2017-8509 is not in CISA KEV. FIRST estimates a 18.24% chance of exploitation in the next 30 days. Check whether you run A remote code execution.
Which versions are affected?
Compare what you have installed with microsoft/office web apps 2010; microsoft/office web apps server 2013. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 18.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Jun 15, 2017 · NIST NVD
Detected
A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8510, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-8506.
Oct 15, 2026 · NIST NVD
Updated
A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8510, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-8506.
Sources
- CVE.orgVulnerability recordCVE-2017-8509
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2017-8509
30-day exploitation probability 18.2%
first.org - NIST NVDVulnerability recordCVE-2017-8509
A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8510, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-850
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.