The issue allows remote attackers to bypass the SafeBrowsing protection mechanism. The estimated number of potentially affected devices and details about real-world incidents are not provided. Technical details about exploitation, such as API endpoints, vulnerable parameters, or function names, are not specified.