Chrome 143 fixes 13 security flaws, plus new Read Aloud and AI features
Google has fixed 13 vulnerabilities in Chrome versions 143.0.7499.40/41 for Windows and macOS and 143.0.7499.40 for Linux. According to Google, none of these vulnerabilities have been exploited for attacks in the wild. This major update brings Chrome up to version 143 and comes one week late with no reason given by Google for the delay.
In the Chrome Releases blog post, Srinivas Sista lists the security vulnerabilities that have been fixed, all of which were reported to Google by external researchers. Google classifies four vulnerabilities as high risk, including a new incarnation of the type confusion issue in the JavaScript V8 engine (CVE-2025-13630). Three other vulnerabilities are classified as medium risk, the rest as low risk.
Table of Contents
What’s new in Chrome 143?
Google is promoting Chrome’s new ability to read web text aloud. To do this, you have to first activate reading mode using the right-click menu and selecting “Open in reading mode,” which opens in a sidebar. At the top of that panel, you’ll now also see options for reading aloud: Play, Voice speed, Voice selection, and Voice highlight.
Google is also integrating more “AI” features into Chrome. You can now access the so-called “AI Mode” of Google Search directly via the address bar and the New Tab page. Gemini in Chrome—the “AI” support that’s now baked into the browser—is designed to summarize text, explain concepts, and answer questions.
Gemini in Chrome will initially be introduced for Windows and Mac users in the US who use English as their default language. Other languages are to come and will be added gradually.
Security fixes in Chrome 143
On November 17th, Google released an emergency update to Chrome 142.0.7444.176 to close a zero-day vulnerability (CVE-2025-13223). On November 20th, Google delivered Chrome 143.0.7499.40/41 for Windows and macOS and 143.0.7499.34 for Android as an early stable update to 0.5 percent of existing Chrome users, but with a one-day delay likely due to the aftermath of the emergency update.
Since then, the release blog and update channels have been quiet. According to schedule, the general release of Chrome 143 would have taken place on November 25th. However, Google did not release Chrome 143 until a week later on December 2nd. Google has not yet given a reason for this. It likely wasn’t due to serious problems with the version distributed with the Early Stable Update, as this is exactly the same version that was previously released to everyone.
Chrome usually updates itself automatically when a new version is available. You can trigger the update check manually using the menu item Help > About Google Chrome. The Extended Stable Channel for Windows and macOS now contains Chromium version 142.0.7499.226. Google does not plan to release Chrome 144 until January 2026.
Other Chromium-based browsers
The makers of other Chromium-based browsers are now required to follow suit with updates. Microsoft Edge, Brave, and Vivaldi are currently at the security level following the emergency update a fortnight ago.
Opera has temporarily reduced its backlog with browser version 124 based on Chromium version 140, which was released on October 13th. The developers have backported additional security patches, namely the fix for the zero-day vulnerability CVE-2025-13223, but overall haven’t come any closer to the desired parity with other manufacturers.
