Skip to content
Server Security Center
KEVhigh8.8

CVE-2016-7200: Microsoft Edge Memory Corruption

Microsoft Edge · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-28.

CVSS v3.1 (CISA ADP)
8.8
high
EPSS (exploit probability, 30 days)
83%
higher than 99.6% of all CVEs
Added to CISA KEV
2022-03-28
US federal due date 2022-04-18
Automatable (CISA SSVC)
no
technical impact: total

CVE-2016-7200 explained

CVE-2016-7200 is a memory corruption flaw (out-of-bounds write) in the Chakra JavaScript scripting engine of Microsoft Edge. A crafted web site can trigger it to execute arbitrary code or crash the browser. CISA lists it as known to be exploited, so unpatched Edge installations are at real risk.

Impact

A remote attacker who gets a user to visit a crafted web site can execute arbitrary code or cause a denial of service. No privileges are needed, but user interaction is required. CISA rates the technical impact as total, meaning full control of the affected component. Exploitation is not considered automatable at scale. Attackers are known to have used this vulnerability.

Who is affected

The CVE record names Microsoft Edge as affected but lists no specific affected versions. It also names no fixed version. This does not mean no fix exists. Consult the Microsoft security advisory for the updates that address CVE-2016-7200.

Written with AI from the data on this page and checked against it automatically.

Official description

The Chakra JavaScript scripting engine in Microsoft Edge allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Scripting Engine Memory Corruption Vulnerability," a different vulnerability than CVE-2016-7201, CVE-2016-7202, CVE-2016-7203, CVE-2016-7208, CVE-2016-7240, CVE-2016-7242, and CVE-2016-7243.

CISA required action: Apply updates per vendor instructions.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: docs.microsoft.com/en-us/security-updates/securitybulleti…
  • CISA's deadline for US federal agencies: 2022-04-18 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply the Microsoft security updates for Edge as described in the vendor advisory.
  2. Follow CISA's required action: apply updates per vendor instructions.
  3. Confirm all managed systems running Edge have received the update.
  4. Warn users against visiting untrusted web sites and following unsolicited links.
  5. Check systems that ran unpatched Edge for signs of compromise.

The CVE record names no fixed version. Use the Microsoft advisory to identify the relevant updates and apply them, as CISA's required action states: apply updates per vendor instructions. Until updates are confirmed installed, limit browsing to trusted sites on affected systems.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-787 Out-of-bounds Write

Questions about CVE-2016-7200

Is CVE-2016-7200 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-28, with a US federal due date of 2022-04-18. Whether it is used in ransomware campaigns is unknown.
How can an attacker trigger this vulnerability?
A user must visit a crafted web site in Microsoft Edge. No privileges are required on the target system.
Which Edge versions should I install?
The CVE record lists no affected or fixed versions. Refer to the Microsoft advisory for the specific updates.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.