LiveActive security incident?Get immediate response
CVE Record

CVE-2018-0876: Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows remote code execu...

Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows remote code execution, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2018-0889, CVE-2018-0893, CVE-2018-0925, and CVE-2018-0935.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a Microsoft Edge remote code execution vulnerability in several older Windows 10 releases and Windows Server 2016. The issue is memory corruption in the scripting engine. If a vulnerable system processes malicious script content, code execution may be possible. The bundle does not provide CVSS, exploit maturity, or detailed remediation text. Exposure is most likely on legacy Windows endpoints or Server 2016 systems where Microsoft Edge is present and can process untrusted web or script content. Organizations with only currently maintained, patched Windows builds are less likely to be exposed, but patch status must be verified against Microsoft guidance. Treat this as high priority for legacy Windows environments because remote code execution in a browser scripting engine can become a user-driven compromise path. The urgency is lower where affected versions are absent or fully patched, but the age of the CVE makes unremediated systems a hygiene concern. Mitigation focus: Review Microsoft’s CVE-2018-0876 advisory for official update guidance.; Prioritize patch verification on listed Windows 10 versions and Windows Server 2016.; Retire or isolate unsupported legacy Windows builds where updates are unavailable..

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-2018-0876 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
2Source links

CVSS and timeline data

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

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Microsoft CorporationMicrosoft EdgeMicrosoft Windows 10 Gold, 1511, 1607, 1703, 1709, 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.