Wrong CN using multiple SAN

This is a known bug, refer to this post for more details: