LiveActive security incident?Get immediate response
CVE Record

CVE-2017-8755: Microsoft Edge in Microsoft Windows 10 1511, 1607, 1703, and Windows Server 2016 allows an attacker to exec...

Microsoft Edge in Microsoft Windows 10 1511, 1607, 1703, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user, due to the way that the scripting engine handles objects in memory in Microsoft Edge, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8649, CVE-2017-8649, CVE-2017-8660, CVE-2017-8729, CVE-2017-8738, CVE-2017-8740, CVE-2017-8741, CVE-2017-8748, CVE-2017-8752, CVE-2017-8753, CVE-2017-8756, and CVE-2017-11764.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a Microsoft Edge remote code execution flaw in older Windows 10 and Windows Server 2016 builds. A malicious web page could run code as the signed-in user if Edge processes the vulnerable content. The bundle includes a public exploit reference, but no cited evidence of active exploitation. Exposure is most likely where legacy Microsoft Edge remains usable on the listed Windows builds, especially endpoints that can browse untrusted websites or open links from email and chat. Supported, fully updated systems are less likely to remain exposed, but patch status must be verified against Microsoft guidance. Treat this as high priority for legacy Windows environments. The business risk is user-context code execution through browser content, with public exploit material referenced. Prioritize confirming patch coverage and removing unsupported browser or operating system exposure. Mitigation focus: Review Microsoft MSRC guidance for CVE-2017-8755 and apply applicable security updates.; Retire or isolate unsupported Windows and Microsoft Edge versions listed as affected.; Limit legacy Edge use for browsing untrusted sites until remediation is confirmed..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-8755 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Microsoft CorporationMicrosoft EdgeMicrosoft Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016.Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.