Vulnerabilities

Vulnerability · CVE-2020-0968

Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability

Published Apr 15, 2020 · catalog updated Jun 16, 2026 · Microsoft Internet Explorer

Patch now

CVE-2020-0968 is in the CISA known-exploited catalog, due May 3, 2022. Confirm Microsoft Internet Explorer against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Gaps on this record

  • No version range is stored. A customer cannot check an installed version against this record.
Severity
High7.5
Known exploitation
CISA KEV and VulnCheck KEV
EPSS
30.68%
Remediation
Remediation guidance
Affected products
cpe microsoft/internet explorer · vendor Microsoft Internet Explorer

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe microsoft/internet explorer11
  • cpe microsoft/internet explorer9
  • vendor Microsoft Internet Explorerversion unspecified

How to fix CVE-2020-0968

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2020-0968 is in the CISA known-exploited catalog, due May 3, 2022. Confirm Microsoft Internet Explorer against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Which versions are affected?

Compare what you have installed with microsoft/internet explorer 11; microsoft/internet explorer 9. Apply updates per vendor instructions.

What should an analyst verify?

CWE-787: Out-of-bounds Write. EPSS 30.68%. The CISA KEV listing is the exploitation evidence. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 15, 2020 · Catalog

    Detected

    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.

  2. Nov 3, 2021 · CISA KEV

    Known exploited

    Apply updates per vendor instructions.

  3. May 3, 2022 · CISA KEV

    Remediation due

    Apply updates per vendor instructions.

  4. Jun 16, 2026 · Catalog

    Updated

    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.

Sources

  • CISA KEVConfirmed exploitationCVE-2020-0968

    Microsoft Internet Explorer contains a memory corruption vulnerability due to how the Scripting Engine handles objects in memory, leading to remote code execution.

    cisa.gov
  • CVE.orgVulnerability recordCVE-2020-0968

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2020-0968

    30-day exploitation probability 30.7%

    first.org
  • NIST NVDVulnerability recordCVE-2020-0968

    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.

    nvd.nist.gov
  • VulnCheck KEVConfirmed exploitationCVE-2020-0968

    Microsoft Internet Explorer contains a memory corruption vulnerability due to how the Scripting Engine handles objects in memory, leading to remote code execution.

    vulncheck.com

References

Freshness

Last verified in this catalog Oct 17, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.