Which products and versions are affected by CVE-2017-8646?

Affected: Edge (Microsoft); Microsoft Scripting Engine versions >= Windows 10 1511, 1607, 1703, and Windows Server 2016.. The full list is in the CVE brief.

Is CVE-2017-8646 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2017-8646 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2017-8646?

Public exploit code is available.

Is there a fix for CVE-2017-8646?

No fixed version is listed yet; check the vendor advisory for mitigations.

How urgently should CVE-2017-8646 be patched?

Brandefense priority: patch immediately, because it is very likely to be exploited soon.

Request A Demo

Vulnerability Intelligence

CVE-2017-8646

HighPublic exploit

Published Aug 8, 2017 · Updated May 12, 2026

Key Facts

Patch immediately

CVE-2017-8646 is a high-severity vulnerability (CVSS 7.5 v3) affecting Edge (Microsoft), Microsoft Scripting Engine.
It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
EPSS estimates a 69% probability of exploitation in the next 30 days.
No fixed version is listed yet; check the vendor advisory for mitigations.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.

CVSS v3

7.5

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS (30-day exploit likelihood)

69%

Higher than 99.3% of all scored CVEs

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

Available

Proof-of-concept or weaponized module

Get the full CVE-2017-8646 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

Microsoft Edge in 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 Microsoft browser JavaScript engines render content when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8634, CVE-2017-8635, CVE-2017-8636, CVE-2017-8638, CVE-2017-8639, CVE-2017-8640, CVE-2017-8641, CVE-2017-8645, CVE-2017-8647, CVE-2017-8655, CVE-2017-8656, CVE-2017-8657, CVE-2017-8670, CVE-2017-8671, CVE-2017-8672, and CVE-2017-8674.

Affected Products

2 affected entries in total

Product	Affected versions	Fixed in
EdgeMicrosoft	See advisory	n/a
Microsoft Scripting Engine	>= Windows 10 1511, 1607, 1703, and Windows Server 2016.	n/a

Timeline

Publicly disclosed
Aug 8, 2017
Last updated
May 12, 2026

Weakness Type

CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

advisory100053
advisory1039095
patchhttps://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8646
exploitExploitDB-42470
other42470

FAQ

Common Questions.

Microsoft Edge in 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 Microsoft browser JavaScript engines render content when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability".
Affected: Edge (Microsoft); Microsoft Scripting Engine versions >= Windows 10 1511, 1607, 1703, and Windows Server 2016.. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
No fixed version is listed yet; check the vendor advisory for mitigations.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.

Is CVE-2017-8646 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.