CVE-2018-0795
Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allow a remote code execution vulnerability due to the way objects are handled in memory, aka "Microsoft Office Remote Code Execution Vulnerability".
Does this matter?
EPSS puts the probability of exploitation in the next 30 days at 19.3%, higher than 97% of all known CVEs. Patch or mitigate before the next change window.
Description
Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allow a remote code execution vulnerability due to the way objects are handled in memory, aka "Microsoft Office Remote Code Execution Vulnerability".
- CVSS 3.0
- 8.8 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS
- 19.27% probability · 97th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Affected
- microsoft/office · microsoft/word
- Source
- secure@microsoft.com
EPSS moved from 18.0% on 21 September 2026 to 19.3% on 27 October 2026. The dashed line is the ten per cent mark our analysts treat as “patch before the next change window”.
References
- http://www.securityfocus.com/bid/102356Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1040153Third Party Advisory, VDB Entry
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0795Patch, Vendor Advisory
- http://www.securityfocus.com/bid/102356Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1040153Third Party Advisory, VDB Entry
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0795Patch, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.