dbcve.org
EdgeWeb browser · Microsoft

CVE-2016-0156

HIGH · 7.5 CVSS v3.0 Published 2016-04-12
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
Microsoft Edge allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Microsoft Edge Memory Corruption Vulnerability," a different vulnerability than CVE-2016-0155 and CVE-2016-0157.

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

Microsoft Edge contains a memory corruption vulnerability in its Chakra JavaScript engine that allows remote attackers to execute arbitrary code or cause a denial of service by tricking users into visiting specially crafted web pages. The vulnerability involves improper memory handling during JavaScript execution, enabling attackers to corrupt memory and potentially achieve code execution.

MitigationApply the Microsoft security update KB3142019 (or later) to address this vulnerability. Organizations should also ensure Microsoft Edge is updated to modern Chromium-based versions, as the legacy EdgeHTML engine containing this flaw has been deprecated.

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 if legacy EdgeHTML is installed
    Open Settings > Apps > Apps & features and search for 'Microsoft Edge', or check for the executable at C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe. The legacy EdgeHTML version uses the EdgeHTML rendering engine.
    Affected if Legacy Microsoft Edge (EdgeHTML) is present on the system - this version contains the vulnerable Chakra JavaScript engine.
  2. Confirm the Edge version type
    Launch Microsoft Edge, go to edge://settings/help, and check the version number. Legacy EdgeHTML versions will show version numbers in the 44.x range (Windows 10 builds). Chromium Edge shows versions like 79 or higher.
    Affected if The Edge version displayed is below 79 (legacy EdgeHTML engine), indicating the vulnerable Chakra JavaScript engine is in use.
  3. Verify Windows version as secondary indicator
    Open Settings > System > About and check the Windows version. Legacy EdgeHTML shipped with Windows 10 through version 1909. Windows 10 version 2004 and later (20H1+) typically replaced legacy Edge with Chromium Edge.
    Affected if Running Windows 10 version 1909 or earlier where legacy EdgeHTML was the default browser.
  4. Check for the Chakra engine component
    On systems with legacy Edge, the Chakra JavaScript engine is built into EdgeHTML.dll located in C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\. This engine processes all JavaScript in legacy Edge.
    Affected if The EdgeHTML.dll file exists in the Microsoft Edge system folder, confirming the vulnerable Chakra JavaScript engine is present.

A system is affected if legacy Microsoft Edge (EdgeHTML/Chakra engine) is installed; the newer Chromium-based Microsoft Edge is not vulnerable to this CVE.

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 KB3142019 (or later) to address this vulnerability. Organizations should also ensure Microsoft Edge is updated to modern Chromium-based versions, as the legacy EdgeHTML engine containing this flaw has been deprecated.

Fix this in Edge Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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