What security update did Google release for Chrome on November 5, 2025?

Google released a security update for Chrome on November 5, 2025, just five days after the previous update. The update patches five vulnerabilities including CVE-2025-12725, CVE-2025-12726, CVE-2025-12727, CVE-2025-12728, and CVE-2025-12729, affecting components such as WebGPU, Views, V8, and Omnibox.

What is CVE-2025-12725?

CVE-2025-12725 is a high-severity vulnerability with a CVSS score of 9.8 affecting WebGPU. It is an out of bounds write vulnerability that allows attackers to write data outside intended memory boundaries, potentially enabling remote code execution through malicious web content.

What vulnerabilities were patched in Chrome 142?

Chrome 142 patches five vulnerabilities: CVE-2025-12725 (out of bounds write in WebGPU), CVE-2025-12726 (inappropriate implementation in Views), CVE-2025-12727 (inappropriate implementation in V8), CVE-2025-12728 (inappropriate implementation in Omnibox), and CVE-2025-12729 (inappropriate implementation in Omnibox). All have CVSS scores of 9.8.

What are the patched Chrome versions for different platforms?

The patched versions are Chrome 142.0.7444.134 or later for Linux, Chrome 142.0.7444.134 or 142.0.7444.135 for Windows, Chrome 142.0.7444.135 for Mac, and Chrome 142.0.7444.138 for Android (which contains identical security fixes).

What is the WebGPU vulnerability in Chrome?

The WebGPU vulnerability is tracked as CVE-2025-12725 with a CVSS score of 9.8 and high severity rating. It is an out of bounds write vulnerability that allows attackers to write data outside intended memory boundaries, potentially enabling remote code execution through malicious web content that exploits the WebGPU graphics API.

What V8 vulnerability was patched in Chrome?

CVE-2025-12727 is a high-severity vulnerability with a CVSS score of 9.8 affecting V8, Chrome's JavaScript and WebAssembly engine. It is described as an inappropriate implementation in V8, though Google is restricting detailed technical information until most users have applied the security patches.

What Omnibox vulnerabilities were fixed in Chrome 142?

Two Omnibox vulnerabilities were fixed: CVE-2025-12728 and CVE-2025-12729, both with CVSS scores of 9.8 but rated as medium severity by Google. Both are inappropriate implementation vulnerabilities affecting Omnibox, Chrome's address bar and search feature.

How do Android users update Chrome?

For Android users, Chrome updates will be distributed through the Google Play Store over the coming days. Android users should check for Chrome version 142.0.7444.138 or later, which contains the same security fixes as the desktop versions.

What is the Views vulnerability in Chrome?

CVE-2025-12726 is a high-severity vulnerability with a CVSS score of 9.8 affecting Views, which is Chrome's user interface rendering and window management system. It is described as an inappropriate implementation in Views, though specific technical details are restricted.

Can attackers execute code through the Chrome WebGPU vulnerability?

Yes, CVE-2025-12725 is an out of bounds write vulnerability in WebGPU that potentially enables remote code execution through malicious web content. Attackers can write data outside intended memory boundaries, which could allow them to execute arbitrary code on the victim's system.

What is the severity level of these Chrome vulnerabilities?

All five vulnerabilities have CVSS scores of 9.8. Google rates CVE-2025-12725, CVE-2025-12726, and CVE-2025-12727 as high severity, while CVE-2025-12728 and CVE-2025-12729 are rated as medium severity despite having the same CVSS scores.

How soon after the previous update was this Chrome security patch released?

This Chrome security update was released on November 5, 2025, just five days after the previous update. The rapid release indicates the critical nature of these vulnerabilities and the urgency for users to apply the patches.

What Chrome version should I update to on Windows?

Windows users should update to Chrome 142.0.7444.134 or 142.0.7444.135 or later. Both versions contain the necessary security fixes for the five vulnerabilities patched in this update.

What Chrome version should I update to on Mac?

Mac users should update to Chrome 142.0.7444.135 or later. This version contains all the necessary security fixes for the vulnerabilities patched in the November 5, 2025 update.

What Chrome version should I update to on Linux?

Linux users should update to Chrome 142.0.7444.134 or later. This version includes patches for all five vulnerabilities disclosed in the November 5, 2025 security update.

How can I manually check for Chrome updates?

Users who do not close their browsers regularly should manually check for updates to ensure they receive critical security patches. This can typically be done through Chrome's settings menu by navigating to Help > About Google Chrome, which will automatically check for and install available updates.

What is V8 in Google Chrome?

V8 is Chrome's JavaScript and WebAssembly engine. It is responsible for executing JavaScript code in the browser. CVE-2025-12727, one of the vulnerabilities patched in this update, affects V8 and is described as an inappropriate implementation with a CVSS score of 9.8.

Advisory

Google releases Chrome update just 5 days after the previous, patches multiple vulnerabilities

Q: What should Chrome users do about these vulnerabilities?

Chrome users are strongly advised to update their browsers as soon as possible to version 142.0.7444.134 or later. Users who do not close their browsers regularly should manually check for updates to ensure they receive critical security patches. The update can be accessed through Chrome's settings menu.

published: Nov. 6, 2025

Take action: If you are using Google Chrome or other Chromium-based browsers (Edge, Brave, Vivaldi, Opera...) patch your browser ASAP. Google wouldn't push a new update so soon unless it's serious. Even if you want to debate the severity scoring, it's better to just update. Because while you debate, hackers will find a way to exploit them.

Learn More

Google has released a security update for Chrome on November 5, 2025, just five days after the previous update.

Vulnerabilities summary:

CVE-2025-12725 (CVSS score 9.8, Google severity High): Out of bounds write in WebGPU that allows attackers to write data outside intended memory boundaries, potentially enabling remote code execution through malicious web content.
CVE-2025-12726 (CVSS score 9.8, Google severity High): Inappropriate implementation in Views that affects the browser's user interface rendering and window management system.
CVE-2025-12727 (CVSS score 9.8, Google severity High): Inappropriate implementation in V8, Chrome's JavaScript and WebAssembly engine.
CVE-2025-12728 (CVSS score 9.8, Google severity Medium): Inappropriate implementation in Omnibox, Chrome's address bar and search feature.
CVE-2025-12729 (CVSS score 9.8, Google severity Medium): Inappropriate implementation in Omnibox.

All Chrome versions prior to 142.0.7444.134/.135 are vulnerable to these security flaws. Users running any version below these build numbers should update immediately.

Patched versions:

Chrome 142.0.7444.134 or later for Linux
Chrome 142.0.7444.134 or 142.0.7444.135 for Windows
Chrome 142.0.7444.135 for Mac
Chrome 142.0.7444.138 for Android (contains identical security fixes)

Google is restricting access to detailed technical information until the majority of users have applied the security patches.

Chrome users are strongly advised to update their browsers ASAP. Users who do not close their browsers regularly should manually check for updates to ensure they receive critical security patches. For Android users, updates will be distributed through the Google Play Store over the coming days.

Google releases Chrome update just 5 days after the previous, patches multiple vulnerabilities

Read More
Android security updates fix three actively exploited vulerabilities
Google releases fix for actively exploited Chrome vulnerability
Lazarus hacker group exploits Windows component to gain …
Researchers warn of critical flaw in iPadOS, macOS …
Apple issues (second) emergency fix for vulnerabilities exploited …