CVE-2018-8174: Double Kill
- Vendor
- Microsoft Corporation
CVE-2018-8174, also known as Double Kill, is a use-after-free vulnerability in the Windows VBScript engine that enables remote code execution through Internet Explorer and applications hosting its engine. During array cleanup, a VBScript object's Class_Terminate callback can preserve a reference to an object whose memory is subsequently freed. Incorrect object-lifetime and reference-count handling leaves a dangling reference that attackers can exploit through object reuse and type confusion to obtain arbitrary memory access and execute shellcode. The vulnerable cleanup path involves VbsErase and the OLE Automation VariantClear function. Affected platforms include multiple Windows client and server releases, including Windows 7, Windows 8.1, Windows RT 8.1, Windows 10, and Windows Server versions from 2008 through 2016. The vulnerability was exploited as a zero-day in April 2018 and subsequently incorporated into multiple exploit kits.
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 allows arbitrary code execution with the permissions of the compromised user, enabling malware installation, data theft, and modification or destruction of accessible data. Administrative users expose the system to broader compromise; exploitation does not inherently grant elevated privileges. Observed campaigns used the vulnerability to deliver ransomware, downloaders, and espionage backdoors, including Magniber, Buran, Purple Fox, CobInt, and SLUB.
Mitigation
If you can’t patch tonight, do this now.
Disable VBScript execution in exposed Internet Explorer contexts and discontinue Internet Explorer use where feasible. Account for applications that embed the Internet Explorer engine: restricting direct browser execution alone may leave document-based attack paths available. Use intrusion prevention or virtual patching to block exploit delivery where immediate patching is not possible. Enforce least privilege and layered web, email, and endpoint protections to reduce exposure and constrain post-exploitation activity.
Remediation
Patch, then assume compromise.
Apply the Microsoft security updates addressing CVE-2018-8174, released on May 8, 2018, or applicable superseding updates for each affected Windows release. The fix modifies the OLE Automation VariantClear cleanup behavior to set the Variant type to VT_EMPTY during deallocation, preventing the demonstrated dangling-reference and object-reuse sequence.
Exploits
4 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 3 not yet analyzed, such as Exploit-DB entries.
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-2018-8174 exploited in the wild?
- Yes. As of Nov 7, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Feb 15, 2022.
- Is there a public exploit for CVE-2018-8174?
- Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2018-8174, the earliest disclosed May 22, 2018.
- Is there a patch for CVE-2018-8174?
- Apply the Microsoft security updates addressing CVE-2018-8174, released on May 8, 2018, or applicable superseding updates for each affected Windows release. The fix modifies the OLE Automation VariantClear cleanup behavior to set the Variant type to VT_EMPTY during deallocation, preventing the demonstrated dangling-reference and object-reuse sequence.
- What products are affected by CVE-2018-8174?
- Microsoft Corporation Windows 7, Microsoft Corporation Windows 8.1, Microsoft Corporation Windows Rt 8.1, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1703, and 5 more.
- How severe is CVE-2018-8174?
- CVE-2018-8174 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 88.2% (100th percentile) as of Nov 7, 2026.
Recent activity
39 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.