CVE-2020-0968: Internet Explorer Scripting Engine Memory Corruption RCE
- Vendor
- Microsoft Corporation
CVE-2020-0968 is a remote code execution vulnerability in the Microsoft Internet Explorer scripting engine caused by improper handling of objects in memory. The flaw is described by Microsoft as a scripting engine memory corruption vulnerability and has been associated with memory corruption in the JScript engine. Available reporting indicates the issue was exploited through crafted web content, including malicious HTML delivered via browser-based infection chains, to corrupt memory and execute attacker-controlled code in the context of the current user. The vulnerability was patched by Microsoft in April 2020 and was reported as exploited in the wild. Based on the available mapping context, the weakness is consistent with an out-of-bounds write leading to memory corruption.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can allow remote code execution in the security context of the current user. If the user has administrative privileges, the attacker may be able to fully compromise the system, including installing malware, modifying data, creating accounts, or moving to follow-on stages such as ransomware deployment. Even without elevated privileges, exploitation can provide an initial foothold and arbitrary code execution sufficient for payload delivery and further privilege escalation attempts. The vulnerability was used in real-world intrusion and malware campaigns, including ransomware-related activity.
Mitigation
If you can’t patch tonight, do this now.
Reduce exposure by disabling or restricting use of Internet Explorer and the legacy scripting engine where operationally feasible. Limit access to untrusted web content, enforce least privilege so browser sessions do not run with administrative rights, and use modern browser isolation and exploit mitigation controls such as DEP/NX and ASLR as defense in depth. Where legacy browser use is unavoidable, constrain it through application control, network segmentation, and tightly scoped allowlisting of trusted sites.
Remediation
Patch, then assume compromise.
Apply Microsoft's security update for CVE-2020-0968 released in April 2020. Prioritize patching all supported systems running Internet Explorer or the affected scripting engine components. Because unsupported platforms may not receive fixes, replace or retire end-of-life systems where the patch is unavailable. Validate that enterprise images, legacy application environments, and compatibility-dependent browser deployments have received the update.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2020-0968 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
- Is there a public exploit for CVE-2020-0968?
- As of Oct 16, 2026, Mallory has found no public exploit for CVE-2020-0968.
- Is there a patch for CVE-2020-0968?
- Apply Microsoft's security update for CVE-2020-0968 released in April 2020. Prioritize patching all supported systems running Internet Explorer or the affected scripting engine components.
- What products are affected by CVE-2020-0968?
- Microsoft Corporation Internet Explorer.
- How severe is CVE-2020-0968?
- CVE-2020-0968 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 30.7% (98th percentile) as of Oct 16, 2026.
Recent activity
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.