Description of the security update for Word 2016: May 8, 2018

Applies to: Word 2016


This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user opens a specially crafted Office file. To learn more about these vulnerabilities, see Microsoft Common Vulnerabilities and Exposures CVE-2018-8161.

Note To apply this security update, you must have the release version of Word 2016 installed on the computer.

Be aware that the update in the Microsoft Download Center applies to the Microsoft Installer (.msi)-based edition of Office 2016. It doesn't apply to the Office 2016 Click-to-Run editions, such as Microsoft Office 365 Home (see Determining your Office version).

Improvements and fixes

This security update contains improvements and fixes for the following nonsecurity issues:
  • When you close an unsaved Information Rights Management (IRM) Office Open XML (OOXML) document, Word claims to be able to "keep unsaved changes," but it actually produces a corrupted .ASD file.
  • Assume that you open a document that is based on an untrusted template (.dotm) in Word 2016. Then, you edit it and create a new document. When you close the first document without saving, Word 2016 freezes.

  • An email message that contains large inline pictures is not displayed correctly in the Outlook client on Windows.

  • When you coauthor a Word document together with another user, the document's normal style can be restricted if you have another restricted style in the document.

  • In Word 2016, you may experience IME composition stopping unexpectedly.

How to get and install the update

Method 1: Microsoft Update

This update is available from Microsoft Update. When you turn on automatic updating, this update will be downloaded and installed automatically. For more information about how to get security updates automatically, see Windows Update: FAQ.

Method 2: Microsoft Update Catalog

To get the stand-alone package for this update, go to the Microsoft Update Catalog website.

Method 3: Microsoft Download Center

You can get the stand-alone update package through the Microsoft Download Center. Follow the installation instructions on the download page to install the update.

More Information

Security update deployment information

For deployment information about this update, see security update deployment information: May 8, 2018.

Security update replacement information

This security update replaces previously released security update KB 4018339.

File hash information

Package name Package hash SHA 1 Package hash SHA 2
word2016-kb4018383-fullfile-x64-glb.exe 106F8E99D03FB1A6781E789EC39860FFAEBC4757 C77A1A8E8D45B804CC9EE042C7469F60E7520448FB168D8E6E0CC7C27FEEC8A5
word2016-kb4018383-fullfile-x86-glb.exe EDA01DC2092E1EF93047996C5D16012624D41E02 BF4CF2EF39B0632EAD23A2F1258449B6595DACD0120FDB19611077F8EBE8EA85

File information

The English version of this security update has the file attributes (or later file attributes) that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.

How to get help and support for this security update

Help for installing updates: Windows Update: FAQ

Security solutions for IT professionals: TechNet Security Support and Troubleshooting

Help for protecting your Windows-based computer from viruses and malware: Microsoft Secure

Local support according to your country: International Support

Propose a feature or provide feedback on Office Core: Office User Voice portal

ERROR: at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited) at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)New URL: about:blank