LiveActive security incident?Get immediate response
CVE Record

CVE-2018-8128: A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory...

A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka "Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-0945, CVE-2018-0946, CVE-2018-0951, CVE-2018-0953, CVE-2018-0954, CVE-2018-0955, CVE-2018-1022, CVE-2018-8114, CVE-2018-8122, CVE-2018-8137, CVE-2018-8139.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2018-8128 is a Microsoft scripting engine memory corruption issue that could allow remote code execution. The source bundle lists Microsoft Edge on Windows 10 versions 1703, 1709, and 1803, plus ChakraCore, as affected. Business risk is highest where legacy Windows or embedded ChakraCore remains in use. Likely exposure is limited to environments still running the listed legacy Windows 10 releases with Microsoft Edge, or applications that include ChakraCore. Organizations on current, fully supported and updated Microsoft platforms are less likely exposed, but should verify asset and patch data. Prioritize as high where legacy Windows or ChakraCore exists. The issue is old, but remote code execution in browser scripting components can create meaningful endpoint compromise risk if unpatched systems remain. Mitigation focus: Review Microsoft’s CVE-2018-8128 advisory for applicable security updates or vendor guidance.; Prioritize remediation for Windows 10 1703, 1709, and 1803 systems.; Identify and update or remove applications that embed ChakraCore..

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-8128 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
MicrosoftMicrosoft EdgeWindows 10 Version 1703 for 32-bit Systems, Windows 10 Version 1703 for x64-based Systems, Windows 10 Version 1709 for 32-bit Systems, Windows 10 Version 1709 for x64-based Systems, Windows 10 Version 1803 for 32-bit Systems, Windows 10 Version 1803 for x64-based SystemsListed
MicrosoftChakraCoreChakraCoreListed
Weakness

CWE details

No CWE listed

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