CVE-2016-0186
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 · uneditedThe 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-0191 and CVE-2016-0193.
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 confidenceMemory corruption vulnerability in the Chakra JavaScript engine in Microsoft Edge allows remote attackers to execute arbitrary code or cause denial of service via a crafted website with malicious JavaScript.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Microsoft Edge is installedCheck for the presence of Microsoft Edge executable (MicrosoftEdge.exe) in the standard installation path (C:\Windows\SystemApps\Microsoft.MicrosoftEdge_*) or via Get-AppxPackage in PowerShellAffected if Microsoft Edge is installed and the system has not received the security update MS16-051 or later
-
Verify security update MS16-051 is installedOpen Windows Update History (Settings > Update & Security > Windows Update > View update history) or run 'Get-HotFix | Where-Object {$_.HotFixID -eq "KB3156421"}' in PowerShell; this specific KB contains the patch for CVE-2016-0186Affected if The update KB3156421 (MS16-051) is NOT listed as installed, meaning the Chakra vulnerability remains unpatched
-
Check Edge version to confirm patch statusLaunch Microsoft Edge, go to Settings > About Microsoft Edge, or navigate to edge://version in the address bar; compare the displayed build number against the fixed build released with MS16-051Affected if The Edge build number is earlier than the version released with MS16-051 patch KB3156421, indicating the vulnerability is present
-
Verify Chakra JavaScript engine DLL versionLocate the Chakra engine DLL (chakra.dll) in the Edge runtime folder (typically C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\Assets\) and check its file properties for version informationAffected if The chakra.dll version matches pre-patch versions and does not reflect the security fix from MS16-051
If Microsoft Edge is in use and the system is missing security update KB3156421 (MS16-051) or later, the Chakra JavaScript engine is vulnerable to CVE-2016-0186 exploitation.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Microsoft security update MS16-051 (or later) to patch the Chakra JavaScript engine vulnerability in Microsoft Edge; until patched, restrict Edge usage and monitor for exploitation indicators.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0186 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-0186 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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