Skip to main content
Mallory
HighVulnerability

CVE-2019-0667: RCE in Windows VBScript Engine (CVE-2019-0667)

Published Apr 8, 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
EPSS31.3%98th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2019-0667CWE-119

CVE-2019-0667 is a remote code execution vulnerability in the Windows VBScript engine. The vulnerability arises from improper handling of objects in memory, which can be triggered when VBScript is processed, typically via Internet Explorer. An attacker can exploit this by convincing a user to visit a specially crafted website or open a malicious file, leading to arbitrary code execution in the context of the current user.

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 allows an attacker to execute arbitrary code with the privileges of the user running the affected application, potentially leading to full system compromise if the user has administrative rights.

Mitigation

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

Disable VBScript in Internet Explorer, especially on systems where it is not required. Use least-privilege user accounts to limit the impact of exploitation. Employ modern browsers that do not support VBScript.

Remediation

Patch, then assume compromise.

Apply the security updates provided by Microsoft to address this vulnerability. The patch corrects how the VBScript engine handles objects in memory.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
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-0667 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2019-0667 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-0667?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2019-0667. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2019-0667?
Apply the security updates provided by Microsoft to address this vulnerability. The patch corrects how the VBScript engine handles objects in memory.
What products are affected by CVE-2019-0667?
Microsoft Corporation Internet Explorer.
How severe is CVE-2019-0667?
CVE-2019-0667 has a CVSS v3 score of 7.5 (High) and an EPSS score of 31.3% (98th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.