If your Chrome installation is still on a version older than the update published on September 3, 2026, you should update it immediately. Google rated CVE-2026-85046 as a high-severity type confusion flaw in V8, Chrome's JavaScript engine, and said it was aware of an exploit for the vulnerability “in the wild.” The fix reached the Chrome 152 stable channel, and on September 8 Chrome 153 moved to stable with an additional set of security fixes.
Which Chrome version fixes CVE-2026-85046?
Google's September 3, 2026 security bulletin ties the fix to the following stable versions. On desktop, Google published 152.0.7977.82/.83 for Windows and macOS and 152.0.7977.82 for Linux. On Android, version 152.0.7977.82 was released with the same security fixes as the corresponding desktop release unless otherwise noted.
| Platform | Version carrying the fix published on Sep. 3 | Stable release published on Sep. 8 |
|---|---|---|
| Windows | 152.0.7977.82/.83 | 153.0.8010.36/.37 |
| macOS | 152.0.7977.82/.83 | 153.0.8010.36/.37 |
| Linux | 152.0.7977.82 | 153.0.8010.36 |
| Android | 152.0.7977.82 | 153.0.8010.36 |
In practice, users on the regular stable channel should install the newest update offered to their device rather than trying to remain on the first build that contained the patch. The September 8 Chrome 153 stable release came after the September 3 security update and included another batch of security fixes.
Do not use “Chrome 153” alone as proof
There is an important nuance that helps avoid a false sense of security: before Chrome 153 was fully promoted to stable, Google had already been distributing Early Stable builds to a small percentage of users. On September 3, for example, build 153.0.8010.27/.28 was announced for some Windows users. That is why checking only the first part of the version number is not the best way to validate the patch.
The simplest rule for most users is to let Chrome check for updates and confirm that the browser is on the stable build currently offered. On September 8, the full stable release was 153.0.8010.36/.37 on Windows and macOS and 153.0.8010.36 on Linux. If the computer uses a corporate channel, Extended Stable, or device management, the rollout cadence may differ and the IT team should be consulted.
How to check the version on Windows, macOS or Linux
- Open Chrome.
- Click the three-dot menu in the top-right corner.
- Go to Help > About Google Chrome.
- Wait for the page to finish checking for updates.
- Read the full version number shown under “Google Chrome.”
- If a Relaunch button appears, use it to apply the downloaded update.
Google's own help page says Chrome checks for updates when the “About Google Chrome” page is open. If an update is pending, it may remain waiting for a browser restart. In other words, seeing that a download has finished is not enough: the browser has to relaunch when prompted before the new build is actually in use.
Why relaunching Chrome matters
Updates are normally downloaded in the background, but the switch to the new binaries happens when the browser is closed and opened again or when the user selects Relaunch. Google says regular tabs and windows are saved and reopened after the process, while Incognito windows are not restored. When an update addresses an actively exploited vulnerability, postponing that relaunch extends the time the old session keeps running vulnerable code.
How to check and update Chrome on Android
On Android, Chrome updates through Google Play. Google's recommended path is Play Store > profile > Manage apps & device, then look for Chrome under available updates. If an Update button is shown, install the available version.
To view the installed version, open Chrome and go to three-dot menu > Settings > About Chrome. Version 152.0.7977.82 was the September 3 release that carried the same security fixes as its corresponding desktop release; on September 8, Chrome 153.0.8010.36 began rolling out on Android.
What about Chromebooks?
On a Chromebook, the browser update is tied to the ChromeOS update. Google's help documentation tells Chromebook users to update the operating system rather than look for a separate Chrome installer. This also means a Chromebook's version should not be mechanically compared with a Windows, macOS or Linux package number: use the ChromeOS update flow and keep the device on the newest stable release offered to it.
What CVE-2026-85046 means for users
Google described the flaw as a type confusion issue in V8 and rated it High severity. The key point for browser users is Google's statement that an exploit already existed in the wild. The bulletin does not need to disclose exploitation details to justify the defensive action: updating and relaunching the browser is the priority.
Google also commonly restricts access to security bug details until a majority of users have received a fix. That practice reduces the amount of information available to people who might try to abuse the vulnerability during the update window.
If the update does not appear or fails
- Close and reopen Chrome, then return to “About Google Chrome.”
- Restart the computer if the update appears to have completed but the version did not change.
- On Linux, use your distribution's package manager if Chrome cannot finish the update through its normal flow.
- On managed computers, company or school policies may control the browser version. Ask the administrator to confirm deployment.
- On unsupported operating systems, Chrome may stop receiving current releases. An unsupported system is not protected simply because the browser still opens.
Quick checklist: are you already protected?
- Did you open Help > About Google Chrome and let the update check finish?
- On desktop, is your version at or above the 152.0.7977.82/.83 level published on September 3?
- On Android, have you received 152.0.7977.82 or a later stable build offered through Google Play?
- If a Relaunch button was shown, did you restart the browser?
- If you use a managed Chrome installation or Chromebook, did you confirm the managed or ChromeOS update path?
Because the vulnerability was already known to be exploited when the bulletin was published, the practical recommendation is straightforward: do not postpone the update. Check the version, install the update, and relaunch the browser.
