Microsoft has released Security Updates (SUs) for vulnerabilities found in:
Exchange Server 2013
Exchange Server 2016
Exchange Server 2019
SUs are available in a self-extracting auto-elev...
Updated Mar 03, 2023
Version 13.0
Blog Post
I installed the February Exchange Security Update for Exchange 2016 CU23 from the download at Microsoft Update Catalog at 09:00 UTC on 15th February 2023. It has been applied to our 40+ Exchange servers.
The build number is 15.01.2507.018
Healthchecker script advises that I don't have the latest build. My understanding is that MS modified the build number since I downloaded the msp, but that is the only difference and it is just semantics (new build number 15.01.2507.021). We can accept the risk that we have a build number mismatch versus the disruption and risk of redeploying.
Heathchecker script also appears to have a flaw regarding detection of:
Bin Search Folder Not Found
I suggest that is addressed by an updated script or listed in the Known Issues with this release section, as two of us have just spent 3 hours troubleshooting this.
We're all only human, but letting such things slip through a release can cause considerable downstream impact.