Google Confirms Chrome 142 Security Fix For 3 Billion Users

[javajolt]

Relaunch Google Chrome now. SOPA Images/LightRocket via Getty Images

Hot on the heels of not just one, but two emergency security updates for the Chrome browser within the space of a single week, details of how attackers targeted the Chrome security sandbox with a zero-day exploit, comes the confirmation of yet another update. This time, Google has disclosed that there are no less than 20 vulnerabilities impacting the Chrome browser. Here’s why you must act now —and how —to ensure your browser is secure.

What You Need To Know About The Google Chrome 142 Security Update

Srinivas Sista, part of the Google Chrome team, has confirmed that Chrome 142 is now being rolled out to three billion users to fix a whole swathe of security issues, including seven high-rated vulnerabilities. In total, 20 vulnerabilities are covered and fixed by this important security update for all Chrome users, other than, as always, those on the iOS platform.

The security updates will become available to Windows, Mac and Linux users across the coming days. The version numbers to look out for are: 142.0.7444.59/60 on Windows, 142.0.7444.60 on macOS, and 142.0.7444.59 for Linux users. While updates are automated, it is highly recommended that you kickstart the process even if your browser isn’t yet showing the restart to update flag. You can do this by heading for the settings menu and selecting About Google Chrome. It is vital to note that you must relaunch your Chrome browser, following the instructions given, because otherwise the update will not be applied and won’t activate the security patch.

And that would mean you will not be protected against the potential attacks that could exploit the vulnerabilities as listed below.

High-rated

   • CVE-2025-12428
     Type Confusion in V8

   • CVE-2025-12429
      Inappropriate implementation in V8

   • CVE-2025-12430
      Object lifecycle issue in Media

   • CVE-2025-12431
      Inappropriate implementation in Extensions

   • CVE-2025-12432
      Race in V8

   • CVE-2025-12433
      Inappropriate implementation in V8

   • CVE-2025-12036
      Inappropriate implementation in V8

Medium-rated

   • CVE-2025-12434
      Race in Storage

   • CVE-2025-12435
      Incorrect security UI in Omnibox

   • CVE-2025-12436
      Policy bypass in Extensions

   • CVE-2025-12437
      Use after free in PageInfo.

   • CVE-2025-12438
      Use after free in Ozone

   • CVE-2025-12439
      Inappropriate implementation in App-Bound Encryption

   • CVE-2025-12441
      Out of bounds read in V8

   • CVE-2025-12443
      Out of bounds read in WebXR

Low-rated

   • CVE-2025-12440
      Inappropriate implementation in Autofill

   • CVE-2025-12444
      Incorrect security UI in Fullscreen UI

   • CVE-2025-12445
      Policy bypass in Extensions

   • CVE-2025-12446
      Incorrect security UI in SplitView

   • CVE-2025-12447
      Incorrect security UI in Omnibox

You know what to do. Check Google Chrome now and ensure you have the latest updates installed and activated.

source