Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2019-1367: Scripting Engine Memory Corruption Vulnerability in Internet Explorer

Published Sep 23, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS52.4%99th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2019-1367CWE-416

CVE-2019-1367 is a remote code execution vulnerability in Microsoft Internet Explorer caused by memory corruption in the legacy JScript engine implemented in jscript.dll. Available technical analysis describes the flaw as a use-after-free condition in which the garbage collector fails to properly track JScript values or callback arguments during Array.sort() processing, including scenarios involving the Enumerator object. Because an object still in use is not rooted correctly, garbage collection can reclaim it prematurely, leaving a dangling pointer that can later be dereferenced. Successful exploitation allows attacker-controlled script delivered through a malicious web page to corrupt memory and execute code in the context of the browser process. The issue affected Internet Explorer 8 through 11 when the vulnerable legacy scripting engine was invoked, including through IE8 compatibility mode.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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 results in remote code execution in the security context of the current user through Internet Explorer. In practical attack chains, the vulnerability was used for drive-by compromise, watering-hole attacks, malvertising, and exploit-kit delivery. An attacker who gains code execution can install malware, access or modify data available to the user, and use the browser foothold as the first stage of a broader chain such as sandbox escape, privilege escalation, persistence, or ransomware deployment. Impact is greater when the victim has administrative privileges or when the flaw is combined with additional local privilege-escalation vulnerabilities.

Mitigation

If you can’t patch tonight, do this now.

Disable the legacy JScript engine where operationally feasible, as Microsoft specifically recommended this as a workaround. Reduce or eliminate use of Internet Explorer, especially legacy document modes and compatibility modes that can force use of jscript.dll. Prevent untrusted or unnecessary sites from rendering in Internet Explorer, restrict Active Scripting in high-risk zones, and use least-privilege user accounts to limit post-exploitation impact. Additional compensating controls include browser isolation, application control, exploit mitigation tooling, and monitoring for suspicious compatibility-mode invocation and exploit-kit style web traffic.

Remediation

Patch, then assume compromise.

Apply Microsoft's security updates for CVE-2019-1367 on affected systems. Because later reporting indicates the initial fix was incomplete and related follow-on issues were addressed in subsequent updates, systems should be brought fully up to date with all cumulative Internet Explorer and Windows security patches rather than relying on a single historical patch level. Organizations should also retire or replace unsupported Windows versions and legacy Internet Explorer-dependent workflows where possible.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
Microsoft CorporationInternet Explorerapplication
FAQ

Frequently asked questions

Is CVE-2019-1367 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-2019-1367?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2019-1367.
Is there a patch for CVE-2019-1367?
Apply Microsoft's security updates for CVE-2019-1367 on affected systems. Because later reporting indicates the initial fix was incomplete and related follow-on issues were addressed in subsequent updates, systems should be brought fully up to date with all cumulative Internet Explorer and Windows security patches rather than relying on a single historical patch level.
What products are affected by CVE-2019-1367?
Microsoft Corporation Internet Explorer.
How severe is CVE-2019-1367?
CVE-2019-1367 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 52.4% (99th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence6Every report linking this CVE to a named adversary.
Associated malware17Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.