The remediation is through Windows Updates. You can install the following updates through WUfB or WSUS. Attached is a list of products and updates if you would like to install the update by creating an application.
I can write the detection script and remediation script, but due to the fact it's a security vulnerability why would you take the risk? I would recommend installing the update through WUfB, WSUS, or download it and create an application. If you create an application make sure you only deploy it to machines with the specified version of Office 2016.
You can build detection logic with using Microsoft QFE.
Product | Article | Download | Build Number |
---|---|---|---|
Microsoft Office 2016 (32-bit edition) | 5002537 | Security Update | 16.0.5435.1001 |
Microsoft Office 2016 (32-bit edition) | 5002537 | Security Update | 16.0.5435.1001 |
Microsoft Office 2016 (32-bit edition) | 5002467 | Security Update | 16.0.5435.1001 |
Microsoft Office 2016 (32-bit edition) | 5002522 | Security Update | 16.0.5435.1001 |
Microsoft Office 2016 (32-bit edition) | 5002469 | Security Update | 16.0.5435.1001 |
Microsoft Office 2016 (32-bit edition) | 5002519 | Security Update | 16.0.5435.1001 |
For Office 2016 (64-bit edition):
Product | Article | Download | Build Number |
---|---|---|---|
Microsoft Office 2016 (64-bit edition) | 5002537 | Security Update | 16.0.5435.1001 |
Microsoft Office 2016 (64-bit edition) | 5002537 | Security Update | 16.0.5435.1001 |
Microsoft Office 2016 (64-bit edition) | 5002467 | Security Update | 16.0.5435.1001 |
Microsoft Office 2016 (64-bit edition) | 5002522 | Security Update | 16.0.5435.1001 |
Microsoft Office 2016 (64-bit edition) | 5002469 | Security Update | 16.0.5435.1001 |
Microsoft Office 2016 (64-bit edition) | 5002519 | Security Update | 16.0.5435.1001 |