Skip to content
Fencer Intel
high 8.8

CVE-2018-0986 in the critical feed json

A remote code execution vulnerability exists when the Microsoft Malware Protection Engine does not properly scan a specially crafted file,…

published 8y ago modified 4mo ago also EUVD-2018-1763

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
63.3%
EPSS 63.3% chance of exploitation in 30 days, percentile 99.2%
public exploits
1
Exploit-DB

Summary

A remote code execution vulnerability exists when the Microsoft Malware Protection Engine does not properly scan a specially crafted file, leading to memory corruption, aka "Microsoft Malware Protection Engine Remote Code Execution Vulnerability." This affects Windows Defender, Windows Intune Endpoint Protection, Microsoft Security Essentials, Microsoft System Center Endpoint Protection, Microsoft Exchange Server, Microsoft System Center, Microsoft Forefront Endpoint Protection.

Patch / fix

Is CVE-2018-0986 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-44402)

Exploit prediction

63.27% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-44402 Microsoft Windows Defender - 'mpengine.dll' Memory Corruption dos, 2018-04-05

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

  • Microsoft Windows Defender
  • Microsoft Windows Intune Endpoint Protection
  • Microsoft Microsoft Security Essentials
  • Microsoft Microsoft System Center Endpoint Protection
  • Microsoft Microsoft Exchange Server
  • Microsoft Microsoft System Center
  • Microsoft Microsoft Forefront Endpoint Protection

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.