Issue has been identified and a fix is being made. It will be rolled out with the next update of SSMS 18.
Fix in a few weeks? That is unacceptable. This should have been caught during testing before the release. what is your suggestion to resolve in the mean time?