dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 18 Apr 2022.
EdgeWeb browser · Microsoft

CVE-2016-7200

HIGH · 8.8 CVSS v3.1 Published 2016-11-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Memory corruption vulnerability in the Chakra JavaScript scripting engine used by Microsoft Edge. Attackers can achieve arbitrary code execution or cause denial of service by tricking users into visiting crafted malicious web pages that trigger the memory corruption condition.

MitigationApply Microsoft security updates for Edge/Chakra (MS16-129 or subsequent cumulative updates). Until patched, restrict or monitor web browsing to untrusted sites.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EdgeWeb browser
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Microsoft Edge is installed
    Check for Edge executable presence: Open PowerShell and run 'Test-Path $env:ProgramFiles\Microsoft\Edge\Application\msedge.exe' or check registry at HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\msedge.exe
    Affected if The test returns False (Edge not installed) means not affected; True means potentially affected and requires further version/patch verification
  2. Determine installed Edge version
    Run 'Get-ItemProperty $env:ProgramFiles\Microsoft\Edge\Application\msedge.exe | Select-Object VersionInfo' in PowerShell, or visit edge://settings/help in the Edge browser
    Affected if Any version number returned indicates Edge is present and potentially vulnerable if not patched
  3. Verify security update MS16-129 is applied
    Check Windows Update history: Open Control Panel > Windows Update > View update history, or run 'Get-HotFix | Where-Object {$_.Description -like "*Security Update*"}' in PowerShell and look for KB3199135 (MS16-129)
    Affected if If KB3199135 or subsequent Edge security patches are NOT listed in installed updates, the system remains vulnerable
  4. Confirm Chakra engine version matches unpatched state
    In Edge, open Developer Tools (F12), go to the Console, and enter 'typeof ChakraCore' or check the Edge version via edge://version to cross-reference with pre-patch build numbers
    Affected if If the Chakra engine version corresponds to builds released before November 8, 2016 (MS16-129 release date), the vulnerability is present

A system is affected if Microsoft Edge is installed and the security update KB3199135 (MS16-129) or a subsequent Edge Cumulative update has not been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch docs.microsoft.com →
Interim mitigation

Apply Microsoft security updates for Edge/Chakra (MS16-129 or subsequent cumulative updates). Until patched, restrict or monitor web browsing to untrusted sites.

Recommended fix High confidence

Windows 10 cumulative security update (November 2016, MS16-129 or later)

  1. Ensure Windows Update is enabled and configured to receive security updates
  2. Run Windows Update to check for and install the latest security patches
  3. For CVE-2016-7200 specifically, install the November 2016 security update (MS16-129) or later cumulative update for Windows 10
  4. After patching, verify Edge version reflects the updated build with the security fix
Caveat Minimal risk - standard Microsoft cumulative security update; may require restart

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Edge Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-7200 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-7200 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data