Thanks for reporting. This already has been fixed in 4.60.3, see details here.