CVE-2017-8510 in the critical feed json
A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office…
published 2017-06-15 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17460
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 22.1%
- EPSS 22.1% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
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-8509, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-8506.
Patch / fix
Exploit prediction
22.13% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Corporation Microsoft Office
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2017-8510
patch, vendor-advisory
-
securityfocus.com
/bid/98813
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1038668
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-8510
- NVD CVE-2017-8510
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.