# CVE-2016-0189: Microsoft Internet Explorer Memory Corruption

> Remote attackers can execute arbitrary code or cause denial of service via crafted websites exploiting memory corruption in Internet Explorer scripting engines.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 28 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 May 2016
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-qw68-vqp7-ff9r

## What is CVE-2016-0189?

CVE-2016-0189 is a high-severity memory corruption vulnerability in Microsoft Internet Explorer, published on 11 May 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Microsoft (1) JScript 5.8 and (2) VBScript 5.7 and 5.8 engines, as used in Internet Explorer 9 through 11 and other products, allow 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-0187.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2016-0189?

It affects 3 products.


Products: Microsoft Internet Explorer, Microsoft Jscript, Microsoft Vbscript.

## How do I fix CVE-2016-0189?

No fix has been published for CVE-2016-0189 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 18 Apr 2022.

## Is CVE-2016-0189 being exploited?

Yes. Attackers have exploited CVE-2016-0189 in the wild since at least 28 Mar 2022, including in ransomware campaigns.

Public exploit code:

- Proof-of-Concept exploit for CVE-2016-0189 (VBScript Memory Corruption in IE11) (github_poc): https://github.com/theori-io/cve-2016-0189
- 对CVE-2016-0189漏洞补丁的分析 (github_poc): https://github.com/deamwork/MS16-051-poc
- Internet Explorer 11 VBScript Engine Memory Corruption (metasploit)
- Microsoft Internet Explorer 11 (Windows 10) - VBScript Memory Corruption (MS16-051) (exploitdb)

## Other vulnerabilities in Microsoft Internet Explorer

- [CVE-2014-1776](https://insights.sbomify.com/CVE-2014-1776/): Microsoft Internet Explorer Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2021-27085](https://insights.sbomify.com/CVE-2021-27085/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0222](https://insights.sbomify.com/CVE-2017-0222/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0210](https://insights.sbomify.com/CVE-2017-0210/): Microsoft Internet Explorer Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2017-0149](https://insights.sbomify.com/CVE-2017-0149/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-0189 and fix it if it is affected.

What it is: CVE-2016-0189 is a high-severity memory corruption vulnerability in Microsoft Internet Explorer, published on 11 May 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2016-0189 in the wild since at least 28 Mar 2022, including in ransomware campaigns.

Affected product: Microsoft Internet Explorer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-0189/ (Markdown: https://insights.sbomify.com/CVE-2016-0189/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-0189
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-0189
- OSV: https://osv.dev/vulnerability/CVE-2016-0189

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-0189/
Summaries are generated and may contain mistakes; the official description above is the record.