This is a bug. The intent is that if the malware check takes too long the system fails "open" and allows the launch. That obviously didn't work correctly in this case.