How severe is CVE-2020-0968?

CVE-2020-0968 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-0968?

Affected package information for CVE-2020-0968 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2020-0968?

No fixed version has been published for CVE-2020-0968 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2020-0968 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2020-0968, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-0968?

CVE-2020-0968 has an EPSS (Exploit Prediction Scoring System) score of 43.7%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2020-0968 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2020-0968 (Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2020-0968?

CVE-2020-0968 is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2020-0968?

CVE-2020-0968 affects microsoft internet explorer (2 versions, e.g. 9, 11). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2020-0968 published, and has it been updated?

CVE-2020-0968 was published on April 15, 2020 and was last updated on October 29, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03

CVE-2020-0968

HIGH

A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'.…

Published

Apr 15, 2020

Updated

Oct 29, 2025

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

43.7%probability of exploitation in next 30 days

High Risk98th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0970.

Affected Products

1 product · 2 configurations

Application

internet explorermicrosoft

2 versions

911

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A remote code execution vulnerability exists in the way that the scripti…

cisa.govCISAJul 2021

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-0968 in your stack?

O3 detects CVE-2020-0968 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works