dbcve.org
EdgeWeb browser · Microsoft

CVE-2016-3386

HIGH · 7.5 CVSS v3.0 Published 2016-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 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-3389, CVE-2016-7190, and CVE-2016-7194.

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 engine in Microsoft Edge allows remote attackers to execute arbitrary code or cause denial of service via a specially crafted website. The vulnerability stems from improper memory handling during JavaScript execution, enabling attackers to corrupt memory and potentially achieve code execution.

MitigationApply the Microsoft security update for CVE-2016-3386 to patch the Chakra JavaScript engine. Until patched, restrict or avoid using Microsoft Edge and implement network-level protections to block malicious JavaScript payloads.

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/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. Identify Windows version and build number
    Open Settings > System > About, or run 'winver' from command prompt, or run 'systeminfo' from command prompt. Note the Windows version and build number.
    Affected if Running Windows 10 prior to the August 2016 security update (KB3172985) is likely affected.
  2. Check Microsoft Edge version
    Open Microsoft Edge, navigate to edge://settings/help, or run 'Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\msedge.exe" -ErrorAction SilentlyContinue | Select-Object -ExpandProperty (Get-Item (Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\msedge.exe" -ErrorAction SilentlyContinue)."(Default)").VersionInfo.FileVersion' via PowerShell.
    Affected if Edge versions prior to version 38.14393.0.0 (released August 2016) are vulnerable.
  3. Verify Chakra JavaScript engine component version
    Locate the Chakra engine file: typically at C:\Windows\System32\chakra.dll. Right-click the file, select Properties, and check the File Version tab, or run 'powershell (Get-Item "C:\Windows\System32\chakra.dll").VersionInfo.FileVersion'.
    Affected if Chakra.dll versions prior to 1.10.0.0 indicate the unpatched vulnerable engine.
  4. Confirm Microsoft Edge is in use
    Check if Microsoft Edge is installed and executable on the system. Run 'Get-Process msedge -ErrorAction SilentlyContinue' via PowerShell, or verify the executable exists at C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe or C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe.
    Affected if Edge is present and used; the vulnerability requires the browser to process malicious JavaScript.

A system is affected if it runs an unpatched version of Microsoft Edge (Chakra engine prior to August 2016 update) and uses Edge to browse untrusted web content.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security update for CVE-2016-3386 to patch the Chakra JavaScript engine. Until patched, restrict or avoid using Microsoft Edge and implement network-level protections to block malicious JavaScript payloads.

Fix this in Edge Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-3386 — 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-3386 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