Should you update to Chrome 152.0.7977.82?
No: install Chrome 157.0.8103.38 instead. Chrome 152.0.7977.82 is a security update Google released on 3 Sep 2026 for Mac, Windows and Linux. It fixes 12 security flaws, 0 rated critical and 10 high by Google.[1] One of them is already being used in attacks.
It has since been replaced by Chrome 153.0.8010.36, released 8 Sep 2026, which includes all of its fixes. If you’re on an older version, install that instead.
Should you update?
No: install Chrome 157.0.8103.38 instead. Chrome 157.0.8103.38 came out on 3 Nov 2026 and includes every fix in Chrome 152.0.7977.82, so there’s no reason to stop at this one. Software Update offers the newest version your device can run.
Is Chrome 152.0.7977.82 still safe?
Not any more. The 13 updates since, up to Chrome 157.0.8103.38, fix 1,372 security flaws that Chrome 152.0.7977.82 doesn’t, and each became public the day its fix shipped. Installing it is safe: get it only from Chrome’s own About page (chrome://settings/help), never from a link in an email, text or pop-up.
What it fixes
Google lists 12 security flaws, 0 rated critical and 10 high by Google.[1] The 10 critical and high ones are:
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-85046 | High | Type confusion in V8 |
CVE-2026-85052 | High | Out of bounds read in CrashReporting |
CVE-2026-85043 | High | Incomplete cleanup in Network |
CVE-2026-85048 | High | Use after free in Compositing |
CVE-2026-85045 | High | Race condition in V8 |
CVE-2026-85050 | High | Out of bounds write in WebGL |
CVE-2026-85053 | High | Improper resource exposure in CacheStorage |
CVE-2026-85042 | High | Use after free in DevTools |
CVE-2026-85049 | High | Use after free in Skia |
CVE-2026-85051 | High | Type confusion in Compositing |
Used in attacks
This fix closes a flaw that attackers were already using before the update came out, either on CISA’s list of flaws being used in attacks or in Google’s own words.[2]
How to update, and how long it takes
A minute or two. Chrome downloads it in the background, and relaunching reopens your tabs.
- Open Chrome’s About page.Type chrome://settings/help in the address bar, or open the ⋮ menu → Help → About Google Chrome. Chrome checks and downloads the update.
- Click Relaunch.Chrome reopens your tabs. Until you relaunch, the old, unfixed version keeps running.
- Do the same in every Chromium browser.Edge, Brave, Opera and Vivaldi are built on the same code and get the same fixes a few days later.
To check it worked: chrome://settings/help shows the version, and says “Chrome is up to date” when it is. It should say 153.0.8010.36 or later.
152.0.7977.75 vs 152.0.7977.82
Chrome 152.0.7977.75, released 1 Sep 2026, fixed 26 security flaws. Chrome 152.0.7977.82 fixes 12 security flaws and includes the fixes before it, so going straight to 152.0.7977.82 gets you both.
- Before: Chrome 152.0.7977.75, 1 Sep 2026, 26 security flaws
- After: Chrome 153.0.8010.36, 8 Sep 2026, 230 security flaws
- Chrome updates, every release and the latest version
- Updates, the latest version of everything HARD tracks
References
- ^ Google. “Stable Channel Update for Desktop”, 3 Sep 2026.
- ^ Cybersecurity and Infrastructure Security Agency. “Known Exploited Vulnerabilities Catalog”.