CVE-2019-1367 Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability
Microsoft Internet Explorer contains a memory corruption vulnerability in how the scripting engine handles objects in memory. Successful exploitation allows for remote code execution in the context of the current user.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 3 Nov 2021.
- CISA lists it as known to be used in ransomware campaigns.
- Rated High severity (CVSS 7.5, scored by CISA).
- It has been in the catalogue for 1,829 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
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-2019-1221.
Affected Versions
| Product | Versions |
|---|---|
| Microsoft Internet Explorer 9 | Windows Server 2008 for 32-bit Systems Service Pack 2 Windows Server 2008 for x64-based Systems Service Pack 2 |
| Microsoft Internet Explorer 11 | Windows 7 for 32-bit Systems Service Pack 1 Windows 7 for x64-based Systems Service Pack 1 Windows Server 2008 R2 for x64-based Systems Service Pack 1 Windows 8.1 for 32-bit systems Windows 8.1 for x64-based systems Windows Server 2012 R2 |
| Microsoft Internet Explorer 11 on Windows Server 2012 | unspecified |
| Microsoft Internet Explorer 11 on Windows 10 Version 1903 for 32-bit Systems | unspecified |
| Microsoft Internet Explorer 11 on Windows 10 Version 1903 for x64-based Systems | unspecified |
| Microsoft Internet Explorer 11 on Windows 10 Version 1903 for ARM64-based Systems | unspecified |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for Microsoft Internet Explorer. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
- 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
Vendor Advisories
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2019-1367 and every other exploited flaw on the list.