# CVE-2017-8549: Microsoft Edge Memory Corruption Vulnerability

CVE-2017-8549 is fixed in 9 products on 1 platform, first by KB4022714, released June 13, 2017. It is not reported as exploited, but the vendor rates exploitation more likely. Patch Radar priority: Urgent.

- Web page: https://patchblox.com/security/cve/CVE-2017-8549
- Priority: Urgent
- CVSS: 4.2 (Critical)
- EPSS: 0.0569
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Vendor exploitability assessment: Exploitation More Likely
- Published: Jun 13, 2017
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2017-8549

## Description

<p>A remote code execution vulnerability exists when Microsoft Edge improperly accesses objects in memory. The vulnerability could corrupt memory in such a way that enables an attacker to execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.</p> <p>An attacker could host a specially crafted website that is designed to exploit the vulnerability through Microsoft Edge, and then convince a user to view the website. The attacker could also take advantage of compromised websites and websites that accept or host user-provided content or advertisements by adding specially crafted content that could exploit the vulnerability. In all cases, however, an attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically by way of enticement in an email or Instant Messenger message, or by getting them to open an attachment sent through email.</p> <p>The security update addresses the vulnerability by modifying how Microsoft Edge handles objects in memory.</p>

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Microsoft | Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1511 for 32-bit Systems | 10586.962 | [KB4022714](https://patchblox.com/security/data/fix/microsoft/kb4022714.md) | Jun 13, 2017 |
| Microsoft | Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1511 for x64-based Systems | 10586.962 | [KB4022714](https://patchblox.com/security/data/fix/microsoft/kb4022714.md) | Jun 13, 2017 |
| Microsoft | Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1607 for 32-bit Systems | 14393.1358 | [KB4022715](https://patchblox.com/security/data/fix/microsoft/kb4022715.md) | Jun 13, 2017 |
| Microsoft | Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1607 for x64-based Systems | 14393.1358 | [KB4022715](https://patchblox.com/security/data/fix/microsoft/kb4022715.md) | Jun 13, 2017 |
| Microsoft | Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1703 for 32-bit Systems |  | [KB4022725](https://patchblox.com/security/data/fix/microsoft/kb4022725.md) | Jun 13, 2017 |
| Microsoft | Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1703 for x64-based Systems |  | [KB4022725](https://patchblox.com/security/data/fix/microsoft/kb4022725.md) | Jun 13, 2017 |
| Microsoft | Microsoft Edge (EdgeHTML-based) on Windows 10 for 32-bit Systems | 10240.17443 | [KB4022727](https://patchblox.com/security/data/fix/microsoft/kb4022727.md) | Jun 13, 2017 |
| Microsoft | Microsoft Edge (EdgeHTML-based) on Windows 10 for x64-based Systems | 10240.17443 | [KB4022727](https://patchblox.com/security/data/fix/microsoft/kb4022727.md) | Jun 13, 2017 |
| Microsoft | Microsoft Edge (EdgeHTML-based) on Windows Server 2016 | 14393.1358 | [KB4022715](https://patchblox.com/security/data/fix/microsoft/kb4022715.md) | Jun 13, 2017 |

---

Data as of 2026-11-07T06:34:28Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo
