High

CVE-2017-8506 — A remote code execution vulnerability exists in Microsoft Office when the software fails to...

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-8510, CVE-2017-8511, CVE-2017-8512, and CVE-2017-0260.

Published Jun 14, 2017 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: microsoft

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 24.2% (30-day exploitation probability)+15
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

24.17%

ahead of 98% of scored CVEs · Oct 15, 2026

Affects

Microsoft

Office and 1 more

CVSS base

7.8

High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — portal.msrc.microsoft.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Microsoft Office, Microsoft Outlook).
Apply the fixed version or the patch documented under Remediation.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
EPSS ahead of 98% of scored CVEs: prioritize it in the patch queue.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Microsoft	Office	version Microsoft Outlook 2010 Service Pack 2, Microsoft Outlook 2013 RT Service Pack 1,	Vulnerable	CVE Program (cve.org) e CISA ADP
Microsoft	Outlook	version 2010-sp2version 2013-sp1version 2016	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

None

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.8	CVSS 3.0	High	1.8	5.9	nvd@nist.gov via NIST National Vulnerability Database
7.8	CVSS 3.0	High	—	—	GitHub, Inc. via GitHub Security Advisories
9.3	CVSS 2.0	High	8.6	10.0	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.

endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · microsoft corporation/microsoft office
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
Fix documented
Oct 15, 2026 · NIST National Vulnerability Database
Affected products added · microsoft/outlook
Oct 15, 2026 · NIST National Vulnerability Database
CVSS changed · 7.8
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Modified
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · Alertas do Telegram
2017
CVE published
Jun 14, 2017 · microsoft

Source activity

Repeated readings are counted rather than listed.

2× References added · Oct 15, 2026 – Oct 15, 2026
1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

5 on the record

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8506
Patch, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
www.securityfocus.com/bid/98811
Third Party Advisory, VDB Entry, vdb-entry, x_refsource_BID, NIST National Vulnerability Database
www.securitytracker.com/id/1038666
Third Party Advisory, VDB Entry, vdb-entry, x_refsource_SECTRACK, NIST National Vulnerability Database
nvd.nist.gov/vuln/detail/CVE-2017-8506
GitHub Security Advisories
github.com/advisories/GHSA-mw6x-vg34-fr9v
GitHub Security Advisories

Elsewhere on this site

Microsoft
every CVE for this vendor

Related CVEs (same products)

High CVE-2026-47293 Microsoft Office Click-To-Run Elevation of Privilege Vulnerability Jun 9, 2026
High CVE-2026-42893 Microsoft Outlook for iOS Tampering Vulnerability May 12, 2026
Medium CVE-2026-42832 Microsoft Office Spoofing Vulnerability May 12, 2026
High CVE-2026-42831 Microsoft Office Remote Code Execution Vulnerability May 12, 2026
Medium CVE-2026-40421 Microsoft Word Information Disclosure Vulnerability May 12, 2026
High CVE-2026-40419 Microsoft Office Click-To-Run Elevation of Privilege Vulnerability May 12, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2017-8506 is "A remote code execution vulnerability exists in Microsoft Office when the software fails to...", rated High. It affects Office (Microsoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 24.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.